Small and medium business | Business Central, N...

Payment Journal Numbering Issue

(6) Share

Report

Posted on by AleAlonso

309

Hello,

I initially configured the payment journal number series with Default No = TRUE, Manual No = TRUE, and Allow Gaps = FALSE. This setup caused an issue where journals created on different days were somehow posted under the same journal number.

To resolve this, I updated the number series to Default No = TRUE, Allow Gaps = TRUE, and Manual No = FALSE. This prevents duplicate postings by triggering an error when a journal is posted with a previously used number, prompting the user to renumber.

However, under this configuration, if a user runs Suggest Vendor Payments, deletes some lines, and then attempts to use the Export File action, they receive the following error: "You have one or more documents that must be posted before you post document no. XXX according to your company's No. Series setup."

Additionally, since all payment journals are meant to go through approval, using No. Series and Posting No. Series in the journal template creates a disconnect in the approval entry as there’s no “pre-assigned number” concept, so it’s difficult to trace the approval entry back to the original journal.

Does anyone know how to configure the number series so that it:

Allows exporting the payment file
Maintains approval history integrity
Prevents multiple journals from posting under the same document number

Thanks

Alejandra

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Alex A 3,072 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

The error you're seeing "You have one or more documents that must be posted before you post document no. XXX..." would likely be triggered by the Allow Gaps = FALSE in combination with Default No = TRUE.

* This setup enforces strict sequential posting, meaning you can't skip or reuse numbers, even if lines are deleted or not posted.

So, when Suggest Vendor Payments generates lines and assigns document numbers, those numbers are reserved. If you delete some lines and try to export, Business Central expects those skipped numbers to be posted first; so you get the error.

Try this:
Default No = TRUE, Manual No = FALSE, and Allow Gaps = TRUE.

This setup ensures:
- Unique document numbers per journal.
- No reusing of posted numbers.
- Export works even if some lines are deleted.

BTW - You want to leave Manual No = False if you can because of the random problems you can get when users aren't being careful.

Was this reply helpful? Yes No
Suggested answer

Sahan Hasitha 2,683 on at

Like (5)

Report
Copy link

Link copied!

hi

To resolve the numbering and approval challenges in the Payment Journal, the recommended approach is to use two separate number series: one for the Document No. and another for the Posting No.. The Document No. series should allow gaps and manual entry, ensuring that approvals are tied to a consistent pre-assigned number and that export processes are not blocked when suggested payments are deleted. The Posting No. series, on the other hand, should be strict with no manual entry and no gaps, guaranteeing unique and sequential posting numbers. This configuration maintains approval history integrity, prevents duplicate postings, and ensures that payment file exports run without errors.

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,420 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @AleAlonso

I agree with your concern there is no control on no. Series . For this purpose you can use Posting No Series column which will keep uniformity in posting Series . Keep manual intervention to No.

And also you can verify this action Renumber Document Numbers. This helps to avoid Posting number error and keep documents aligned .

if you feel this helped , pl mark Verified

Regards

Pallavi Phade

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,219 Super User 2026 Season 1 on at

Like (5)

Report
Copy link

Link copied!

This is a pain point with Payment Journal numbering + approvals + file export in Business Central.

1. That error occurs because Allow Gaps = TRUE + Manual No. = FALSE means BC enforces strict sequential usage of the number series.
> When you delete some suggested lines, there is now a "gap" between the numbers assigned and the ones that will post, BC expects the deleted numbers to be used first, hence it throws the error.

2. Challenges with Approvals & Pre-assigned Numbers

> Payment approvals are tied to the Line No. and Document No. at the time of approval.

> If Document No. is re-assigned at posting (because you use Posting No. Series), the approval entry loses its 1:1 traceability to the posted ledger entry.

3. Recommended Best Practice

The ideal setup is to use two separate number series:

Document No. Series > Assigned when the journal is created (used for approvals & file export).

Posting No. Series > Assigned at posting (used in G/L entry).

But with payment journals, we want one consistent number across approval, export, and posting, so we can’t just rely on Posting No. Series.

4. Optional: Add Customization for "Pre-Assigned Number"
> If you absolutely must not allow gaps (for audit compliance), a small customization or Power Automate flow can:
> Reserve a number when Suggest Vendor Payments is run.
> Release the number if the journal is canceled.
> Ensures fully sequential, gapless numbering even when lines are deleted.

Thanks

Rishabh

Was this reply helpful? Yes No
Suggested answer

Valentin Castravet 32,210 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Best practice is to use separate number series for different batches. Essentially each batch has its own number series. This solves your issue and is better for an audit trail.

I wouldn’t use different posting number series, that adds unnecessary complexity.

Valentin Castravet
Work: Zander ERP Services
Blog: Dynamics 365 Business Central Insights
LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Nimsara Jayathilaka. 4,950 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!
Hi Alejandra

Set Manual Numbering: Manual No = TRUE, Default No = FALSE on the payment journal template.

Allow Gaps: Allow Gaps = TRUE to prevent errors when lines are deleted or modified.

Pre-Assign Numbers: Ensure journal numbers are assigned before approval to maintain history integrity.

Separate Series for Export (Optional): Use a dedicated number series if needed for exported payment files.

Check Before Posting: Make sure all lines are ready and numbered to avoid “must be posted” errors.

Thanks

Nimsara

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,090 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi, hope the following can give you some hints.

Dynamics 365 Business Central: How to combine the No. Series with the date (No Customization)

https://yzhums.com/16424/

Thanks.

ZHU

Was this reply helpful? Yes No