Document numbers and amounts can match in 1C Accounting (BP) and UNF while bank balances differ. Finding the cause requires moving beyond document cards to active movements for each account and checking the native data exchange.
On 23 October, KMVSG performed this diagnosis in read-only mode. Specific missing operations fully explained the difference. Documents, posting states and synchronization settings were not changed at this stage.
1C exchange diagnosis
From a balance difference to the source operation
- 01Period
- 02Movements
- 03Matching
- 04Cause
- Accounts are compared at the same point in time.
- The posting flag is checked alongside active register movements.
- A recovery plan follows confirmation of the cause.
Fix the entity, accounts and point in time
Reconciliation requires the same bank accounts, legal entity and time cutoff. A total covering all cash cannot be directly compared with bank balances: the included sources must be explicitly defined.
The October audit read bank movements from Accounting and UNF. For each of seven accounts, the equation “opening balance + movements = closing balance” was checked independently, with a zero residual. This established internal consistency before investigating differences between databases.
Check movements, not just the posting flag
The Posted flag describes a document state. To determine its effect on a bank balance, read the active movements for the relevant register and account. One examined receipt was marked as posted but had no active bank movements.
That document was excluded from the operations explaining the difference. Creating another movement just because a document is posted could introduce an error. Payment orders, bank receipts and withdrawals must also be matched according to their different roles.
Build a complete explanation from source documents
The current difference was fully explained by 23 missing movement-generating documents: 18 withdrawals, three receipts and two internal transfers. Both sides of transfers were retained in the plan. A separate receipt and withdrawal offset each other in the total but remained necessary for a complete history.
Earlier deposit-operation differences were checked separately: they cancelled each other out and did not explain the new discrepancy. This separates the current cause from known historical migration differences.
Inspect exchange settings and logs
UNF settings showed that the native BP-to-UNF exchange had been disabled after errors, automatic startup was off and no schedule was set. The last receipt and send shown in the interface were dated 1 September. Logs contained successful runs followed by exchange errors and database-update status messages.
The current Accounting update result was checked separately: the update and additional procedures had completed successfully. A historical message therefore could not be presented as the current database state. Independent post-processing does not replace the native import of missing documents either.
Agree recovery after diagnosis
The audit delivered a confirmed cause of the lag and a plan for specific operations. Restoring the exchange and correcting documents were outside this work. Before restarting it, check documents already imported manually: matching objects may have different numbers.
Next, agree the legal entity and exchange direction, restore the native process and compare documents and registers again. Only then determine which operations are still missing. An arbitrary adjustment for the total difference does not restore the original history. This is a technical review of a specific exchange; accounting treatment and corrections must be agreed with the responsible specialist.
Quick checklist
- Choose the same entity and time cutoff
- Match bank accounts
- Check the balance equation in each database
- Read active movements for disputed documents
- Check the native exchange and its latest jobs
- Agree the plan and repeat reconciliation before making changes
Links and source code
This article covers: 1C Accounting UNF reconciliation, 1C bank movements, Data exchange diagnosis, Data controls.