Restricted -> Unrestricted

And just FYI, the time that dictates if a pledge is current or future is set up in system tables > t_defaults > Future Receivable Cutoff

Here is the documentation for that entry

The value for this entry can be either a number of days after the pledge date or it can be a fixed date (like the end of the current fiscal year).  If it is a fixed date, then any pledge payment scheduled after that date will be recorded as Future Receivable.  If no entry exists in T_DEFAULTS, the system will behave as in past versions, calculating one year from the pledge date.

The reason you would want seperate GLs for resticted vs unrestricted is so the monies would be distinguishable to the finance department.  If you use the same GL for both, there really isn't much point in using the restricted functions since the posting records won't distinguish the money in any way.

Leslie is correct about future to current but there is an addition to this.  The determination of Future vs Current can be based either on a relative date (anything due to be paid more than 12 months in the future) or it can be based on a fixed date.

We use the second method.  We set the cutoff date for current payments to be the end of the fiscal year.  This means that any payment which is due in a future fiscal year, regardless of when it is received, will be placed in a Future status.  In other words, if someone makes a pledge for a future campaign and we expect payment after July 1 (the next fiscal year) it will be Future, even if the pledge is made in the last week of June.

There is a great webinar on financial reconciliation with development from a couple of years ago:  http://www.tessituranetwork.com/network/Learning/Webinars%20Archive/Finance/Financial%20Reconciliation%20Contributions.aspx

This helped solidify my understanding of the GL setup and I think will answer a lot of your questions.

We have our FUTURE_RECEIVABLE_CUTOFF set to a date many years out and I still have payment schedules entries being created with a Future receivable status when they are 12 months after the contribution date.

I have tried entering a set date with the format as yyyy-mm-dd and mm/dd/yyyy and even mm/dd/yyyy hh:mm:ss with no change.  I also tried using a number of days rather than a set date and I still can't get the Future setting to differ from 12 months out.  Even when trying to go the other way and set the cutoff date to 30 days the schedule entries only change when 12 months out.

Is there anything else in the system that figures into this problem?

Two things to check. 

I don't think the label should have underscores (i.e. "FUTURE RECEIVABLE CUTOFF"). This is a maddening inconsistency in T_defaults.

The other thing to check (if you are in a consortium environment) is whether there is another entry with the parent table set to a specific organization with a value that is overriding the one you are changing.

Hope this helps!

Aha, perfect!  Getting rid of the underscores was the exact fix I needed.

This is a great heads up for everyone because the General Ledger Accounts documentation shows underscores.

Thanks again for the help.

Kevin, you are incredible.  Thank you.