← Back to Stories

Story · Solution

The accountant has the contractor list right months before it is due

I am the outside accountant for a small coffee roaster.

Sound familiar?

The year-end contractor list is built in the last days, from three systems, with the same person under two names.

Why it hurts

I am the outside accountant for a small coffee roaster. Contractor forms are due at the start of each year, and every year the list was built in the last days before the deadline. Payments sit in the books, in PayPal and in the payroll system. The same person can appear under two names, and the forms we need from contractors arrive weeks after we ask. The deadline is too late to find any of this out.

How it is solved

Have, months before the deadline, the full list of contractors who will need a form: what each was paid, from every source, what each one still needs, and nothing on the list that does not belong there.

  1. The accountant gathers payments from every source. The app collects what each contractor was paid this year from the books, from PayPal, from Stripe and from the payroll system, and shows the source beside every amount. The list only reads and changes nothing.
  2. The accountant sees the same person under two names flagged, never merged. Payees are combined only where the name and the email match exactly. Where two similar names may be the same person, both are flagged with each total and the combined total, so the accountant decides.
  3. The accountant finds that what does not belong is kept out. A personal payment sent through PayPal to friends and family is not on the list, and neither are transfers to the business's own bank account.
  4. The accountant sees each contractor placed in its own section. Contractors at or above the year's reporting threshold, those near it, and corporations are each listed in their own section, and those below the threshold in another. None is silently dropped. Each contractor carries the status of its tax form, and one paid only through the payroll system is listed with that source.
  5. The bookkeeper has the requests for missing forms drafted. An AI agent drafts a request for the contractor's tax form wherever it is missing, and the app fills in each payee's name and what was paid. A payee whose form is already on file is refused by name. Drafting sends nothing and stores nothing.
  6. The accountant chooses whom to ask, and the owner approves each request. The accountant ticks the contractors to ask. The owner then reads each request, edits it if needed, and approves it. The approval is recorded with who gave it and when. In the demo the send is simulated and labelled as such.

Works with

PayPal, Stripe

The result

Every contractor who will need a form, each with what it needs: the amount from every source, the section it belongs in, and a form request drafted where the form is missing, approved by the owner before it is sent. Personal payments and transfers to the business's own account are kept out. The forms come back months ahead, and the deadline becomes a check rather than a hunt.

  • If a contractor passes the threshold with a form on file, they are ready to file.
  • If a contractor passes the threshold with no form, a request is drafted months before it is needed.
  • If a contractor is a corporation or sits just under the threshold, they are listed in their own section, never silently dropped.

Try it

The demo runs on WidgetCo Coffee Roasters, an example business: a coffee roaster with an online store and a wholesale side. You will see it as Marta, the outside accountant.

Connected to this story