What Your DSP Bookkeeper Isn't Catching — And Why It's Not Their Fault

Your bookkeeper is good at their job. They balance your books, categorize expenses, run payroll, prepare taxes, and keep your P&L accurate. If you have a dedicated DSP accountant or bookkeeping firm, they probably understand Amazon's billing structure better than most.

But there's a gap between what bookkeeping covers and what Amazon's billing system requires — and that gap is where DSP owners quietly lose money every month. It's not a competence issue. It's a structural one.

What Bookkeepers Do Well

A good DSP bookkeeper handles the financial backbone of your operation:

• Categorizing revenue and expenses from bank statements
• Payroll processing for drivers and dispatchers
• P&L preparation and monthly financial reports
• Tax preparation and compliance
• Cash flow management and forecasting
• Recording settlement deposits and matching them to periods

This work is essential. Without it, you're flying blind on the financial health of your DSP. A skilled bookkeeper keeps the operation solvent and compliant.

Where the Gap Lives

The gap isn't about what bookkeepers know — it's about what data they have access to and when they see it.

They work from outputs, not inputs

Bookkeepers work from bank statements and settlement PDFs. They see the final numbers — what Amazon deposited and what the settlement report summarized. They don't see the inputs: the route-level delivery data in WST, the real-time fleet records, or the individual deduction details that produced those final numbers.

When the settlement says "Variable Pay: $38,000" and the deposit is $37,400, the bookkeeper records the deposit and notes the difference. But they have no way to determine whether the $600 gap is a legitimate deduction, a billing error, or a dropped route — because that requires cross-referencing data in portals they don't access.

They don't have portal access

Reconciliation requires logging into Amazon's logistics portal to pull WST data, checking Payee Central for deposit records, reviewing the FlexPayments portal for invoice details, and cross-referencing fleet management data. These are operational systems that bookkeepers typically don't have credentials for — nor should they. These portals contain sensitive operational data, driver information, and security credentials.

Even if a bookkeeper had access, navigating four different Amazon portals weekly isn't a reasonable addition to a bookkeeping scope of work. It's a different function entirely.

Timing doesn't align

Most bookkeeping happens on a monthly cadence — monthly close, monthly P&L, monthly bank reconciliation. Amazon's dispute windows are 7-14 days. By the time the monthly bookkeeping cycle reviews a settlement, the dispute window for that period closed two to three weeks ago.

Even bookkeepers who work on a weekly cadence are still reviewing settlements after the fact. Catching a dropped route on Thursday when the invoice appeared on Monday means you've already burned half the dispute window before anyone looked at it.

The data volume exceeds manual checking

A 30-route DSP generates roughly 150-210 route records per week, each with package counts, shipment types, and distance data. Checking each of those against the settlement's variable pay calculation isn't a 15-minute task — it's a 2-3 hour exercise that requires line-by-line comparison across two different data formats.

Multiply that by deposit reconciliation, deduction verification, and scorecard tier checks, and you're looking at 4-6 hours of reconciliation work per settlement period. No bookkeeper has that kind of bandwidth allocated to a single client.

Reconciliation Is a Separate Function

The distinction matters: bookkeeping records what happened. Reconciliation verifies that what happened was correct.

Your bookkeeper records that Amazon deposited $37,400 on Friday. Reconciliation checks whether that deposit should have been $38,000 based on the routes your drivers actually completed, the incentive tier your scorecard actually reflects, and the deductions that were actually legitimate.

These are parallel functions, not sequential ones. Reconciliation doesn't happen downstream of bookkeeping — it runs alongside it, feeding verified numbers into the same financial picture.

What This Means in Practice

The solution isn't firing your bookkeeper or finding a "better" one. It's recognizing that reconciliation is a distinct process that requires:

• Access to Amazon's operational portals (WST, Payee Central, FlexPayments, fleet management)
• Weekly cadence aligned with settlement periods, not monthly close
• Cross-referencing capability across 13 billing categories and 4+ data sources
• Speed — disputes need to be filed within 7-14 days of invoice appearance

Some DSP owners handle this themselves. Some delegate it to an operations manager. Some use specialized tools. The method matters less than the recognition that it needs to happen — and that expecting your bookkeeper to catch billing errors with bank statements and settlement PDFs is asking them to do a job they weren't given the tools to do.

Your bookkeeper keeps your books clean. Reconciliation keeps Amazon honest. Both matter. They're just not the same thing.