Batch posting is how revenue reaches the general ledger for contracts running in subledger mode. Draft subledger lines stay out of the ledger until you group them into a revenue recognition batch and post it. A batch aggregates many lines into a single journal entry per company and currency, so you replace hundreds of individual entries with one per company and currency combination each period.
Prerequisites
Before you post a batch, confirm the following.
- One or more contracts are set to subledger recognition mode and have generated draft subledger lines.
- The periods you intend to post are open in your period locking configuration.
- You know whether your organization requires approval for revenue recognition batches, which changes when lines actually post.
Preview a batch with a dry run
Start every posting cycle with a dry run so you can review exactly what will hit the general ledger before anything is written. The preview computes batches from your filters without persisting them.
- Open Revenue Recognition → Batches and select Create batches.
- Set the period range for the revenue you want to post.
- Narrow the scope with the optional company, customer, and contract filters.
- Review the previewed batches. DualEntry groups the matching draft lines into one batch per company and currency, showing the aggregated amount, line count, and affected contracts for each.
- Expand a previewed batch to inspect its individual subledger lines, and exclude any lines you are not ready to post.
The dry run persists nothing, so you can adjust filters and re-preview as many times as needed. When the preview matches what you intend to recognize, continue to posting.
Post the batch
Posting converts the previewed batches into real general ledger activity. From the preview, select Post batches to execute.
DualEntry claims the matched lines, creates one revenue recognition batch per company and currency, and generates the backing journal entry with the aggregated GL entries. Posted lines move to posted status and link to the batch that posted them. Concurrent posting is safe: DualEntry locks the matched lines while it posts, so two people cannot claim the same lines into different batches.
What happens next depends on your approval configuration.
- No approval configured. Lines are marked posted immediately and the general ledger reflects the revenue right away.
- Approval configured. DualEntry creates the batch in a draft state and sends it to the approval queue. Lines are claimed by the batch but stay in draft until an approver acts.
Only posted batches affect the general ledger and recognized revenue reports. Draft lines and batches awaiting approval have no GL impact, so revenue you have previewed but not posted will not appear in the revenue waterfall or recognized revenue reports. Approve or reject a batch
When approval is required, a posted batch waits in the Inbox approval queue until a reviewer decides. The batch shows an approval status badge on both the batch list and the batch detail page.
- Approve. All lines in the batch move from draft to posted and the general ledger transaction is created.
- Reject. The batch is archived, its lines are released back to unclaimed draft, and the reviewer’s comment is shown on the batch. The released lines are available to batch again once any blocking issue is resolved.
Approvers can act from the Inbox or directly on the batch detail page. Until the batch is approved, its lines remain claimed, which blocks change orders and terminations over the affected periods, as described in Revenue Subledgers.
Review batches
Browse posted and pending batches from Revenue Recognition → Batches. The list shows each batch’s company, currency, period range, aggregated amount, line count, and approval status.
Open a batch to see the filters used to create it and a paginated table of its subledger lines, with links to each line’s contract and performance obligation. A GL impact tab shows the resulting journal entry. This gives auditors a direct path from a single aggregated journal entry back to every contract and obligation it covers.
Archive a batch
Archiving a batch reverses a posting when you need to redo it. Open the batch and select Archive. DualEntry releases the batch’s lines back to draft so they become available for batching again.
Archiving a batch is one-way. There is no recovery of the archived batch record, though its released lines can be posted again in a new batch.
Next steps
- Revenue Subledgers explains recognition modes, subledger lines, catch-ups, and the guards that protect posted periods.
- Approval workflows covers how to configure who approves revenue recognition batches.
- Reporting shows where posted revenue appears once a batch is on the general ledger.
