Build vs Buy: Marketplace Accounting Automation

By TallySutra Team · 13 August 2026 · 5 min read

Any competent developer can write a script that turns an Amazon settlement report into Tally import files, which is exactly why so many sellers and a fair number of CA firms have one, usually written by a cousin, a freelancer, or a technically inclined partner. The script works, for a while, and the build-versus-buy question seems settled until the first report format change lands. This article takes the decision seriously in both directions: what building really commits you to, what buying really buys, and a framework for choosing that is honest about the hidden line items on each side.

What you are actually building

The visible work is parsing files and emitting vouchers, perhaps two weeks of effort for the marketplaces you sell on. The invisible work is everything that makes the pipeline trustworthy over years:

• Format maintenance: marketplaces change report layouts without notice, and every change is an urgent, unplanned fix, because the books are waiting.
• Settlement reconciliation: converting sales reports is the easy half; matching settlements to orders at order level, itemising fees, and handling cross-period returns is where the logic lives, and where scripts usually stop.
• Duplicate safety: the same file will eventually be run twice. Idempotent imports must be designed, not assumed.
• Exception handling: rows that do not parse or match need somewhere to go other than a log file nobody reads.
• Workflow and controls: review before posting, an approval record, per-client separation for firms, none of which a script provides by default.
• Continuity: the author leaves, and the pipeline becomes an unmaintainable dependency with the books attached to it.

What buying actually buys

A purpose-built product amortises all of the above across its whole customer base: format changes are the vendor's problem, reconciliation depth and duplicate safety are product features rather than backlog items, and workflow, review, exceptions, multi-client structure, comes built in. The trade-offs are equally real: a subscription cost, dependence on a vendor's roadmap and longevity, and less flexibility for genuinely unusual requirements. Evaluating vendors on exactly these risk dimensions, including how your data is handled (see TallySutra's security page for how we approach it), is part of the buy decision, and our buying guide covers the evaluation criteria and the factual landscape of available tools.

The decision framework

The honest reading of that table for most sellers and CA firms: the requirements are standard, the engineering capacity is borrowed, and the controls are non-negotiable, which points one way. The build case is real but narrow: it belongs to businesses with unusual requirements and a standing engineering function that treats the pipeline as a product with an owner, tests and a roadmap, not a script with an author.

The hybrid worth considering, and the trap

A sensible hybrid: buy the pipeline, keep your analysis layer. Let a product handle ingestion, reconciliation, exceptions and posting, then build whatever dashboards and channel analytics you like on top of clean TallyPrime data, custom work that is genuinely differentiating, cheap to maintain, and not load-bearing for the books. The trap to avoid is the reverse hybrid, a bought import utility plus home-built reconciliation, which recreates the hardest maintenance burden while paying a subscription too. If reconciliation is the need, buy reconciliation, not conversion with reconciliation as your homework; the depth difference is laid out in order-level versus summary reconciliation. And before any build decision, run the cheap experiment: a month of your real reports through an existing product's pilot tier, TallySutra's is free, on pricing, tells you precisely what you would be rebuilding, and whether the parts your script skips, exceptions, duplicate safety, review, were the parts you actually needed. Whichever way you decide, revisit the decision on a calendar rather than in a crisis: an annual half-day review of costs, incidents and vendor health keeps the choice deliberate, and is far cheaper than re-deciding mid-emergency after a format change breaks the books in a filing week.

Frequently asked questions

Related reading

• Marketplace Accounting Mistakes That Cost Sellers Money
• The Multichannel Seller's Accounting Guide
• Reconciliation Exceptions: How to Resolve Them