Files and APIs
Payment data arrives in different formats and needs manual normalization.
Structure transactions, fees, references, and payer context.
Connect payment processors and bank files to Sanka workflows for payment records, invoice matching, refunds, fees, payouts, and accounting handoff.










































%201.png)




Bring payments, payouts, fees, refunds, disputes, balances, remittance files, and bank statements into Sanka.
Match payments to invoices, customers, orders, subscriptions, and AR balances.
Send partial payments, fees, overpayments, refunds, and duplicate candidates to review before handoff.
| Workflow | Without Sanka | With Sanka |
|---|---|---|
| Files and APIs | Payment data arrives in different formats and needs manual normalization. | Structure transactions, fees, references, and payer context. |
| Reconciliation | Name variance, partial payments, fees, and refunds block matching. | Store candidates, confidence, differences, and review queues. |
| Accounting | Payouts, fees, refunds, and tax evidence are prepared late. | Prepare accounting-ready context before close or export. |
Payment data arrives in different formats and needs manual normalization.
Structure transactions, fees, references, and payer context.
Name variance, partial payments, fees, and refunds block matching.
Store candidates, confidence, differences, and review queues.
Payouts, fees, refunds, and tax evidence are prepared late.
Prepare accounting-ready context before close or export.
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.