For Mariana, the lesson is simple: No third-party sync lasts forever. The only reliable connection is the one you control. Today, she’s building her own API connector. Because the last mile of the ledger shouldn’t belong to a product manager’s roadmap.
Then, in the fall of 2016, her CPA mentioned a whisper: GoPayment . Intuit’s mobile solution. Mariana envisioned a clunky card-swiping dongle and sighed. But she tried it.
Then, the silence began.
But the field was a different beast. Out there, clients paid with checks that blew away in the wind or cash that required a frantic drive to the bank. Her crew used paper invoices that got lost in truck glove compartments. The "last mile" of her accounting—the moment money actually changed hands—was a chaotic, un-auditable mess.
One Tuesday, she called Intuit support. The tech, polite but robotic, delivered the euphemism: "GoPayment is now primarily designed for QuickBooks Online ecosystem. Legacy Desktop sync is on a maintenance-only cadence." quickbooks gopayment desktop
A new transaction, already categorized as "Service Income." The customer name "Patricia Hendricks" was already linked to her existing profile. The funds were marked as "Undeposited Funds"—exactly where she wanted them before a bank reconciliation. No double-entry. No manual receipt pile. No Excel spreadsheet acting as a purgatory between the real world and the ledger.
She treats GoPayment as a standalone terminal now. At the end of each day, she reconciles the GoPayment settlement report against her bank feed inside Desktop. The magical sync is dead. But the data is still true. For Mariana, the lesson is simple: No third-party
Her crew? They use a different app—a simple Stripe terminal that dumps a clean CSV into a shared folder. She’s built a small Python script (she learned to code, out of spite) that converts the Stripe CSV into an IIF file that QuickBooks Desktop swallows whole.