Automated payroll reconciliation.

Data flows one way. Fulfil imports your processed Gusto pay runs and posts them as journal entries; nothing is sent back to Gusto. Every pay run lands in your books without manual data entry.

Each processed pay run, whether regular or off-cycle, becomes a single journal entry dated on the check date, with the pay period start and end dates in the description. It records gross pay, net pay, employee and employer taxes, benefits, reimbursements, and child support. Entries post as aggregate totals, not per-employee lines.

You map each Gusto payroll item to a GL account once during setup, covering wages, benefits, taxes payable, and the cash account Gusto debits when it runs payroll. Fulfil filters each field to accounts of the required type. After mapping is done, new pay runs post automatically.

Fulfil checks Gusto for new processed pay runs automatically and deduplicates by Gusto's payroll UUID, so the same run is never imported twice. You can also pull historical pay runs on demand using a date-range filter.

No. Once your payroll items are mapped, each pay run posts itself as a journal entry. You skip the manual wage and tax entries for standard runs.

Some Gusto adjustment payrolls, such as post-payrun tax corrections, do not carry enough detail for a fully balanced entry, so Fulfil imports them in Draft with a system note. Review and balance those under Finance > Ledger > Journal Entries before posting. Other pay runs keep importing normally in the meantime.