Introduction

Payroll SaaS founders obsess over disbursement — getting salaries to employee bank accounts on payday. Finance teams obsess over what happens after: audit trails, downloadable statements, and reconciliation when someone disputes a payment.

On Anchor, salary payout uses bulk transfer (batch NIP payouts). Proof of payment uses transaction history and statements — the reporting layer HR products need to sell into enterprise finance buyers.

This article covers the reporting side for payroll & HR platforms building on Anchor in Nigeria.

Payroll architecture on BaaS

Employer uploads payroll run in your HR SaaS
        ↓
Your ledger validates amounts + beneficiaries
        ↓
Bulk transfer API → employee bank accounts (see Week 4)
        ↓
Transaction history + statements → finance download
        ↓
Webhooks confirm final per-employee status

Disbursement without reporting is a feature. Disbursement with audit trails is a product finance will buy.

Why HR SaaS needs statements

Stakeholder	Need
HR admin	"Did everyone get paid?"
Finance	Month-end close, auditor requests, tax prep
Employee	Payslip matches bank credit
Enterprise buyer	Compliance evidence

Anchor's payroll use case (getanchor.co) explicitly includes statements for payroll audit trails alongside accounts, payouts, and transfers.

Step 1 — Design payroll references (before reporting)

Every salary line in a bulk transfer should carry a traceable reference:

payroll_{runId}_employee_{employeeId}

When finance pulls transactions later, they filter by payroll_jan2026_* and reconcile against the uploaded payroll file.

This is engineering discipline — not an Anchor-specific trick — but BaaS makes it worthwhile because transfer records live in one system.

Step 2 — List account transactions

After a bulk payroll run, fetch transactions on the source account.

const ANCHOR_KEY = process.env.ANCHOR_SANDBOX_KEY!;
const BASE_URL = process.env.ANCHOR_BASE_URL ?? "https://api.sandbox.getanchor.co";

async function listPayrollAccountTransactions(accountId: string) {
  const res = await fetch(
    `${BASE_URL}/api/v1/accounts/${accountId}/transactions`,
    {
      headers: {
        accept: "application/json",
        "x-anchor-key": ANCHOR_KEY,
      },
    }
  );

  if (!res.ok) {
    throw new Error(`Transactions fetch failed: ${res.status}`);
  }

  return res.json();
}

Verify path and query params (from, to, pagination) in accounts & transactions docs.

Payroll tip: Store bulkTransferId from the disbursement step. Cross-reference with individual transfer IDs in the bulk response when building per-employee status in your app.

Step 3 — Generate statements

Anchor supports statement generation for deposit accounts — typically used in live environment for PDF/Excel/HTML exports via dashboard; API access may use the statements endpoint (verify current spec at docs.getanchor.co).

Example shape from Anchor developer examples:

curl --request POST \
  --url "$ANCHOR_BASE_URL/api/v1/statements" \
  --header 'content-type: application/json' \
  --header "x-anchor-key: $ANCHOR_SANDBOX_KEY" \
  --data '{
    "data": {
      "type": "DepositAccount",
      "attributes": {
        "productName": "CURRENT"
      },
      "relationships": {
        "customer": {
          "data": {
            "id": "CUSTOMER_ID",
            "type": "BusinessCustomer"
          }
        }
      }
    }
  }'

Important: Confirm the current statements request body in official docs before production — payload fields evolve.

HR product UX: Expose "Download payroll period statement" in your admin — trigger generation for the employer's Anchor account covering pay date range.

Step 4 — Finance reconciliation workflow

Recommended flow for payroll SaaS:

Pre-run: Employer approves payroll in your UI
Disburse: POST /api/v1/transfers/bulk with employee beneficiaries
Track: Webhooks bulkTransfer.completed + per-transfer NIP events
Reconcile: Match failed transfers → notify HR to fix bank details
Report: Pull transactions for pay period → generate statement → attach to payroll run record
Archive: Store PDF/CSV in your document store for 7-year retention policies

Embedded finance for SaaS founders (Space #2 tie-in)

Payroll is the clearest embedded finance story for B2B SaaS:

You already own the employer relationship
Salary runs are recurring and high-trust
Finance buyers ask about audit trails on day one

Anchor gives disbursement (bulk/NIP) + accounts + statements without a bank partnership.

Production checklist

Unique references per employee per payroll run
Bulk transfer status before generating "paid" payslips
Statement date range aligned to pay period
Role-based access: HR sees summary, finance sees full export
Employee-facing: link payslip to transfer reference