File parsing
Without Sanka
Every format change creates another copy-paste risk
With Sanka
Structure payment date, payer, amount, memo, and reference fields
Let Codex turn payment files into matched cash application
Upload bank statements or payment CSVs. Codex reads the file, creates payment records, maps them to invoices, customers, and deals, then sends only exceptions to review.
Ask anything...
Cash Application
Changes will appear here
Trusted by 1,000+ teams
Overview
Cash application from file upload to invoice matching
Parse payment files
Upload bank statements, settlement CSVs, or payment reports, then read payment date, payer, amount, memo, and fees.
Map to invoices automatically
Match open invoices by invoice number, customer name, amount, payment date, and reference data.
Review exceptions only
Partial payments, fees, duplicate payments, and mismatches stay visible for human review.
Workflow
From Codex instruction to reconciled payments
- 01Upload the payment fileProvide a bank statement, Stripe payout, or transfer list.
- 02Read columns and line itemsExtract payment date, payer, amount, memo, fee, and reference number.
- 03Create payment recordsCheck duplicates and required fields, then create payment records in Sanka.
- 04Map to open invoicesUse customer, invoice number, amount, and date to link payment candidates.
- 05Route exceptionsSave unmatched, partial, fee-adjusted, or duplicate candidates for review.
Compare
Reading a spreadsheet is not the same as closing cash application
| Workflow | Without Sanka | With Sanka |
|---|---|---|
| File parsing | Every format change creates another copy-paste risk | Structure payment date, payer, amount, memo, and reference fields |
| Payment records | Spreadsheet review does not become an operational record | Create payment records linked to the source file and executor |
| Invoice matching | Name variation, fees, and partial payments slow matching down | Suggest invoice matches with confidence and reason codes |
| Exception review | Payments that need review get lost in the batch | Queue unmatched, mismatched, and duplicate records for owners |
| Audit trail | It is hard to explain who matched what and why | Store file, records, match reason, status changes, and history |
Payment records
Without Sanka
Spreadsheet review does not become an operational record
With Sanka
Create payment records linked to the source file and executor
Invoice matching
Without Sanka
Name variation, fees, and partial payments slow matching down
With Sanka
Suggest invoice matches with confidence and reason codes
Exception review
Without Sanka
Payments that need review get lost in the batch
With Sanka
Queue unmatched, mismatched, and duplicate records for owners
Audit trail
Without Sanka
It is hard to explain who matched what and why
With Sanka
Store file, records, match reason, status changes, and history
Customer quotes
Customer stories from Sanka teams
We want inventory, sales management, tax, and accounting to connect smoothly while keeping operating cost and time low.
Sanka does more than inventory control. It can manage purchasing, billing, orders, and shipping in one place.
We used to place orders with artisans via email or phone, which often led to losing track of order details or forgetting orders altogether.
FAQ
Frequently asked questions
What files can Codex process?
Typical files include bank statements, payment service payout CSVs, and transfer lists. Sanka can structure the required fields even when column names differ.
Can automatic matching be controlled?
Yes. High-confidence matches can proceed while mismatches, partial payments, fee differences, and duplicates are routed for review or approval.
Can invoice status be updated?
Yes. Payments can be linked to invoices and update status such as paid, partially paid, or needs review.
What is stored in the audit log?
Sanka can store the source file, created payment records, matched invoices, exception reason, executor, and status change history.