An internal payment accounting and control system
Invoices and payments were tracked in scattered places, and reconciliation with accounting cost hours and bred errors. We built storage, search and automatic reconciliation against 1C.
- Client
- A company reconciling payments by hand
- Industry
- Finance
- Year
- 2026
- Duration
- In production, with a roadmap
Invoices and payments were tracked in scattered places, and reconciling the data with the accounting system cost a lot of manual time and was prone to errors.
What we did
and why we did it that way.
Structured storage
A single base of payment documents with search, status sorting and filtering by document.
A full record cycle
Create, edit, search and delete records. User authorisation and access control.
Automatic reconciliation with 1C
A module matches the system data against 1C exports and surfaces discrepancies: missing invoices, extra unpaid items, mismatched amounts.
Import and export
Data exchange through Excel. On the roadmap: a web version with multi-user access and a role model.
What changed
and what we measured it with.
How it went
day by day and week by week.
- Brief
Types of discrepancy
Worked out exactly where the data diverges from accounting.
- Build
Accounting and reconciliation
Built the record storage and the matching module against 1C.
- Production
Manual control gone
Replaced the manual reconciliation with an automatic one and cut the error risk.
How it looks
in schematics.
These are screen schematics. We do not publish client interfaces without permission
A similar problem
on your side?
Describe it in the brief. In working hours we come back with an estimate of time and cost within two hours.