EQD: PayByLink Payments Can Post To The Actual Payment Date's Period Instead Of The Current System Period
🔵 Overview PayByLink payments imported into A/R can now post to the G/L period matching the date the payment was actually received, instead of always posting to whatever period AR happens to be set to at the time of import. This is a configurable option, not a forced change — clients relying on the current behavior are unaffected unless the option is turned on for them.
Navigation: AR Configuration, Department Maintenance, Consultant Setup, or Client Maintenance > PayByLink tab
The Two Posting Period Options
- A/R current period (default) — PayByLink payments post to whatever G/L period AR is currently set to at the time of import. This is the original behavior.
- Calculate from date — PayByLink payments post to the G/L period matching the actual date the payment was received or settled, regardless of what period AR is currently set to.
Where To Turn It On
- Go to the PayByLink tab under AR Configuration (system-wide), Department Maintenance, Consultant Setup, or Client Maintenance.
- Set Posting Period to Calculate from date to enable the new behavior, or leave it at A/R current period to keep the existing behavior.
- Save.
💡 Note Like other DBPay overrides, this setting follows the Client > Consultant > Department > System-wide hierarchy — a level with no override set falls back to the next level up.
Example: Payments Posting To Different Periods
With Calculate from date enabled, PayByLink and credit card transactions received around a period crossover land in the period matching their own payment date, rather than all landing in whatever period is currently open — as shown in the Prd/Yr column below.
What This Doesn't Affect
- Manually charged AR payments (for example, a cash payment entered through AR Receipts Editing) are unaffected — staff have always been able to set the period at entry for these, and that continues to work exactly as before.
- Regular OE invoice posting to AR is unaffected. This setting only controls how PayByLink payments import into AR — it has no effect on the normal posting of an OE invoice.
Frequently Asked Questions
Q: What are the two Posting Period options for PayByLink?
A: A/R current period (the default) posts PayByLink payments to whatever G/L period AR is currently set to at import. Calculate from date posts to the G/L period matching the actual payment date instead.
Q: Where do I turn this on?
A: On the PayByLink tab, at AR Configuration (system-wide), Department Maintenance, Consultant Setup, or Client Maintenance.
Q: If I enable this for one client, does it affect other clients?
A: No. It follows the same Client > Consultant > Department > System-wide override hierarchy as other DBPay settings — only records with the option explicitly set are affected.
Q: Does this affect manually charged AR payments?
A: No. Those already support setting the period at entry and continue to work the same.
Q: Does this affect how OE invoices post to AR?
A: No. This setting only affects how PayByLink payments import into AR; regular OE invoice posting is unrelated.
Q: What happens if the calculated period is already closed or locked?
A: This edge case is still being scoped internally as of this writing and hasn't been finalized — confirm current behavior before relying on it in a period-close scenario.
Tags: paybylink, pbl, posting-period, gl-period, ar-import, calculate-from-date, ar-current-period, period-close