Checked transactions
One combined CSV of accepted transaction rows, retaining original filename and source row for tracing.
For small teams with matching sales-export CSVs: I combine validated transactions, calculate totals by customer and product, and list rejected records instead of silently counting them.
Fixed-scope manual fulfillment. No subscription, account access, or software installation required from the buyer. Sample data are fictional—not customer projects or sales results.
One combined CSV of accepted transaction rows, retaining original filename and source row for tracing.
Totals for matching customer/product codes: total quantity and calculated amount (quantity × unit price).
Missing fields, invalid dates, ambiguous names or duplicate source files are listed for review, not hidden.
The five-row sample has three valid transactions and two rejected rows (one blank quantity, one nonexistent calendar date). Accepted total: KRW 55,000. These are actual test-engine examples, not real client data.
All example files are UTF-8 CSVs with a BOM, not XLSX. Some spreadsheet programs may remove leading zeros from product codes unless you explicitly import codes as text.
거래일, 거래처코드, 거래처, 상품코드, 상품명, 수량, 단가 (date, customer code/name, product code/name, quantity, unit price). Column order may differ. The public offer does not yet include flexible header mapping or automatic translation.The Gumroad product describes a 50% deposit at checkout and 50% balance upon completion. The payment processor's current checkout display, fees, FX rates and terms control the actual transaction. Confirm the exact input scope and timing first.
View Gumroad product / ordering →
Opening the product link does not pay or create an order.
Share only the header names, estimated file counts/sizes and desired totals. Please do not paste personal data, transaction records, account numbers or passwords.
A FormSubmit anti-spam check may appear. Alternative: email the operator directly.