Close, reconcile and report

G/L reconciliation

Reconcile commission to the general ledger line by line, give every difference a reason, and sign off only when the evidence is unchanged and nothing differs.

updated: Oct 8, 2026applies-to: 1.1.2.0

With a Bitta Commission reconciliation you prove that what the commission subledger expected to post is exactly what reached the general ledger. For each posted accounting proposal, the Commission Reconciliation card compares every commission accounting entry with the G/L entry it produced, line by line, and gives every difference a reason. You can sign off a reconciliation only when the evidence is unchanged and there are no differences.

Before you start

The accounting proposal must be Posted. See Commission accruals.
You need the finance-all security scope. Only the role that owns reconciliations, the Bitta Commission Accountant permission set, can create, build, refresh or sign off a reconciliation. Users with the Bitta Commission Auditor permission set can open them read-only.
When Posting Enabled is on in Commission Posting Setup, Require Reconciliation must be on too.

What is compared

When a proposal posts, the app links each commission accounting entry to the G/L entry it created. A reconciliation reads those links and the G/L entries with the proposal's document number and source code.

Field	Meaning
Source Total / Subledger Total	The sum of the net debit positions per G/L account of the commission accounting entries.
G/L Total	The same sum for the linked G/L entries and any unlinked G/L entries of the proposal.
Matched Count / Matched Total	The comparisons that agree, and the source total when everything matches.
Difference Count / Difference Total	The exception lines and the sum of their absolute differences.
Tolerance Amount	Always zero for a reconciliation created from a proposal.
Evidence Hash	A fingerprint of the filters, the comparisons and the totals.

Step 1: Create and build the reconciliation

On the posted Commission Accounting Proposal, choose Create reconciliation. If the proposal already has a reconciliation, it opens. Otherwise a new zero-tolerance reconciliation opens in Draft, dated on the proposal's posting date.

Commission Reconciliation card in status Draft for a posted proposal, with zero totals, blank comparison filters and an empty comparisons part — *Step 1: a new draft reconciliation.*

Optional: choose Set comparison filters to limit the comparison to certain G/L accounts, dimension sets or currencies. The values appear as Account Filter, Dimension Filter and Currency Filter. Blank compares everything. Filters can be set only while the reconciliation is in Draft.

Filter dialog for the reconciliation scope with Account No., Dimension Set ID and Currency Code filter fields of the posting proposal lines — *Step 2: optional comparison filters.*

Choose Build reconciliation. The app freezes one comparison per accounting entry and adds an exception for every G/L entry of the proposal that has no link to a commission accounting entry. The status becomes Matched when every comparison agrees, or Exceptions when differences remain.

Commission Reconciliation in status Matched with source, subledger and G/L totals and Reconciliation Comparisons lines marked MATCHED — *Step 3: the built reconciliation.*

Step 2: Read the comparisons

The Reconciliation Comparisons part lists every comparison:

Field	What it shows
Expected Account No. / Actual Account No.	The account in the commission subledger, and the account on the G/L entry.
Expected Amount LCY / Actual Amount LCY / Difference Amount LCY	Both amounts in local currency and their difference.
Expected Posting Date / Actual Posting Date	The posting date the accounting policy resolves, and the date on the G/L entry.
Match Status Code	MATCHED or EXCEPTION.
Reason Code	AMOUNT, ACCOUNT, POSTING-DATE, DIMENSION, CORRECTION, MISSING-LINK or UNLINKED-GL.
G/L Entry No.	The linked G/L entry. Choose G/L entry to open it in General Ledger Entries.
Subledger Entry No.	The commission balance ledger entry this accounting line reproduces.
Resolution Reference	The reference recorded when an exception was resolved.

The app checks amount, account, posting date, dimension set and correction lineage in that order, so a line with both an amount and an account difference shows AMOUNT. MISSING-LINK means the accounting entry has no single linked G/L entry. UNLINKED-GL means a G/L entry carries the proposal's document number and source code but was not created by the commission posting.

The expected posting date follows the closed period behavior of the accounting policy, so an entry that was posted into the next open period reconciles against that date.

Resolve exceptions

A difference usually has a cause outside the commission posting, for example a manual journal posted with the proposal's document number. Correct the cause in Business Central, then record what you did:

Select the exception line and choose Record resolution.
On Commission Posting Details, enter the Evidence reference: a correcting journal number, a ticket or a short explanation. Choose OK.

A line can be resolved only once, and only while the reconciliation is not signed off. The frozen comparison does not change.

WARNING

Recording a resolution does not clear the exception. A reconciliation with exceptions cannot be signed off.

Step 3: Validate, refresh and sign off

Choose Validate reconciliation. Commission Finance Validation lists any line or evidence hash that no longer reproduces, any G/L entry or accounting entry that changed since the build, and every exception line. Nothing changes.

Commission Finance Validation opened from Validate reconciliation, with no findings for a matched reconciliation — *Step 1: review the evidence.*

Optional: choose Refresh comparison totals on a reconciliation in Matched or Exceptions that is not signed off. The app rebuilds the comparisons in memory and refreshes the totals only if every frozen comparison still reproduces exactly. If anything changed, the refresh is refused and the totals stay as they were. The original evidence hash is kept in the audit trail.
Choose Sign off reconciliation. It is available only in status Matched. The app validates the evidence again and records the sign-off. The status becomes Approved, and Approved At is filled in.

Commission Reconciliation in status Approved with zero difference count, the evidence hash and the approved at date and time — *Step 3: a signed-off reconciliation.*

Reconciliation statuses: Draft, Running, Matched, Exceptions, Approved, Closed and Cancelled. Reconciliation lines are append-only: only the resolution reference can be added after the build.

Find reconciliations

Search for Commission Reconciliations to see every reconciliation with its status, totals and sign-off time, or choose Reconciliations on an accounting proposal to see its own. Posting proposal on the card opens the proposal.

Commission Reconciliations list with number, status, as of date, source total, G/L total, difference count, difference total and approved at — *All reconciliations in one list.*

Reconciliation and period close

The Commission Period Close Checklist has a Reconciliation Zero gate. It passes only when the period has at least one reconciliation and no reconciliation of the period has a difference total above its tolerance. See Close a period.

Troubleshooting

BAA-ACC-RECON-FILTER. A comparison filter has invalid syntax.
BAA-ACC-RECON-RESOLUTION-STATE. Only an unresolved exception line of an unsigned reconciliation can be resolved.
"Only a posted proposal can be reconciled." Post the proposal first.
"Frozen reconciliation evidence no longer reproduces exactly." A G/L entry, accounting entry or document context changed after the build. Investigate the change with Validate reconciliation.
"Only a valid zero-difference reconciliation can be signed off." Validation found exceptions or changed evidence.

For the accounting reports, see Commission reports.

What's next

Deliver the results to your salespeople: Earnings statements.