Divide one payment
Transaction split workpaper
Divide one payment across categories, keep the original row separate and check that the parts add up to the cent. Runs in your browser.
This tool processes your file and entries in this browser tab, without uploading or saving them.
Which payment are you splitting?
Use a decimal point without grouping. Preserve the original sign: a -100.00 parent needs signed children totaling -100.00. A blank amount is not zero.
Privacy and clearing your input
This tool does not send your file contents to a server or save them in browser storage. Use Clear or reload to clear the active input. Navigating away and Back may restore uncleared contents. Download and print actions, where offered, create copies only when you choose them. Your browser manages temporary memory and any separate print window. The PDF converter has its own upload workflow.
Divide it into categories or people
Use the parent's sign. No amount is adjusted automatically, even when the difference is only one cent.
Source read: waiting for complete parent details.
Allocations: enter a label and value for every part.
Arithmetic: not available yet.
Equal totals do not validate the categories or receipts. This is not a debt settlement, expense claim, journal entry or bank-import file.
Split one payment into categories or people, then check that the signed parts add back to the original exactly. Keep the original in a separate control file so it cannot become an extra spend row in the allocation export. Free, browser-local and no signup.
By AnyStatement
Published , 5 min read
Keep the payment and its explanation separate
Type one parent amount, date and payee, or select exactly one row from a CSV. Supply its account and currency, give each of two to 20 parts a category or person label, and record the receipt details or agreed basis if you have them. This tool explains one amount at a time; it does not settle debts between people or build a reimbursement request.
Preserve the signed parent amount. For a -120.00 payment, -72.35 and -47.65 are complete allocations: their signed total is -120.00 and the residual is 0.00. If your source uses positive amounts for purchases, keep that sign consistently instead. The tool does not infer your bank's convention.
CSV input needs a signed amount column. If the source has separate debit and credit columns, use the debit/credit converter first. Choose the date and number conventions, then confirm the selected row against the source. Other records are retained in the preview, not added to this calculation. Rows with findings cannot be selected.
Decide where the last cent belongs
Exact amount mode never adjusts a part to make the total look right. A nonzero residual blocks export. Correct a missing item, discount or typing error using your supporting records, rather than hiding the difference in the last category. Mixed-sign amounts need a separate confirmation because a charge and a refund can offset while still adding up.
Percentages must total exactly 100%, with up to two decimal places. For equal thirds, use shares of 1, 1 and 1 rather than three entries of 33.33%. Shares are positive whole-number weights from 1 to 1,000,000. Both percentage and share modes require you to choose a remainder rule.
Largest remainder: calculate each absolute share, keep its whole cents, then distribute leftover cents to the largest fractional remainders. Ties go to earlier parts. Finally restore the parent's sign. Equal weights on -100.00 give -33.34, -33.33 and -33.33.
Last part receives the remainder: round each earlier absolute share to the nearest cent, with exact halves rounded up, and give the last part whatever remains. Restore the parent sign afterward. This rule can make the last part smaller or larger than its independently rounded share. If the earlier rounded parts would exceed the whole amount, this rule is blocked; choose largest remainder instead.
The article's $31.75 household portion
The payment-splitting article starts with a fictional -100.00 purchase: groceries 54.25, household supplies 31.75 and desk supplies 14.00. Its display table uses positive costs. This tool uses signed allocations, so that whole purchase would have children -54.25, -31.75 and -14.00.
Load example focuses only on the household portion, not on another bank payment. Rowan, Taylor and Sam share -31.75 equally. With the last-part rule, Rowan and Taylor get -10.58 each and Sam gets -10.59. Their total is -31.75, with a 0.00 residual. Changing the portion to -31.76 gives -10.59, -10.59 and -10.58 under that same rule.
The choice of who carries the rounding difference comes from the people sharing the cost, not the calculator. Their allocations explain the household portion; they are not three new purchases and do not establish who still owes money.
Two files, not one doubled total
The child-allocation CSV contains only the parts. Every child keeps a parent ID, a child ordinal, its own workpaper ID, the selected source line and the allocation basis. These IDs link worksheet rows; they are not bank FITIDs. Use distinct parent IDs when combining separate workpapers.
The original/control CSV contains one parent, the child total and the residual, plus all original cells from the selected row. Never add its parent amount to the child-allocation amounts. The source CSV is untouched. Print summary opens a separate snapshot that does not update when you change or clear the tool; close it when finished.
Downloads quote CSV fields and prefix formula-like text with an apostrophe. The changed-cell count is shown, while validated signed numbers keep their numeric form. Unmapped original cells are treated as text, not assumed to be numeric. The exports are new working copies, not byte-for-byte source backups or destination-app import templates.
Arithmetic is the check, not the category decision
This tool handles one parent and two to 20 children at a time. A UTF-8 CSV can contain up to 5,000,000 bytes and 10,000 data rows. Supported currencies are USD, EUR, GBP, CAD, AUD, NZD and CHF, all at two decimal places here. Greater precision is rejected rather than silently rounded. Separate accounts or currencies are never totaled together.
A zero residual means only that the supplied allocations sum to the supplied parent. It does not validate receipts, category choices, document authenticity, fairness, tax deductibility or reimbursement eligibility. No receipt upload, AI inference, automatic journal entry or accounting connection is involved.
Your file and the values you enter are processed in this browser tab. They are not uploaded or sent to analytics. We do not save them between visits. Downloads you choose to save remain on your device. Clear removes active input and decisions, but is not a secure memory wipe. Back navigation may restore uncleared state.
We opened OWASP's CSV injection guidance on 18 October 2026; it showed no update date. It notes that spreadsheet save-and-reopen behavior can remove formula protection, so no CSV escaping method guarantees safety in every application. The fictional amounts were independently recomputed with decimal arithmetic. No spreadsheet or live accounting import was tested.
If you only have the PDF statement
For one payment, typing it from the statement may be quickest. For a longer history, first ask the bank for a native CSV. If only PDFs remain, AnyStatement can extract transaction rows for review. That is a separate upload workflow; this free workpaper never sends it your local input. 3 pages a day without an account or card. The free allowance is shared per network and resets at midnight UTC. Conversion is a separate upload; this tool does not send its contents there.