Skip to content

Payroll

Payroll Access, Privacy, and Current Limits

Understand who can access payroll, which data to exclude, what the current product supports, and how to resolve common payroll issues.

Payroll contains sensitive employee information. GrantLink’s current payroll workspace, chat tools, imports, evidence, and reports are available only to organization admins. Ordinary organization members and viewers cannot read or change payroll detail.

Include:

  • a stable employee ID and display name;
  • payroll run, pay-period, and pay-date information;
  • supported earning components and exact amounts;
  • one legal entity and USD currency; and
  • evidence that supports where work occurred.

Exclude Social Security numbers, bank details, home addresses, birth dates, tax elections, medical information, and unrelated HR records. Do not paste payroll detail into public report links or general notes.

CSV headers and cells are untrusted content. They cannot instruct the assistant, change access, or bypass server validation. The assistant proposes a column mapping; deterministic code validates the original file and computes exact cents.

Current Supported Boundary

GrantLink currently supports CSV payroll-register imports, employee/component costs, Initiative evidence, eligible-grant allocation, exact-cent unresolved remainders, immutable corrections, employee-by-grant reports and snapshots, and read-only QuickBooks line matching.

It does not currently support:

  • payroll-provider connectors or XLSX imports;
  • payroll calculation, paychecks, tax filing, or native timekeeping;
  • deductions, employee withholding, net pay, liabilities, negative reversals, taxes, benefits, or fringe pools;
  • non-USD, mixed-currency, or multiple-entity files;
  • partial acceptance of a file containing malformed or unsupported rows;
  • expected-payroll calendars or program-lead request delivery;
  • payroll report PDF/workbook export or external submission;
  • a visual QuickBooks line picker or payroll journal creation;
  • payroll-specific roles beyond admin-only access; or
  • payroll replacing effective actuals in every existing dashboard and report.

This product has been verified with synthetic data in the repository. Do not treat that as customer, payroll-provider, or production validation.

Common Problems

Answer only when you know the fact, and name the person or source that confirms it. If the export layout changed, review the new mapping instead of assuming the old one still applies.

The file does not import

Read the reported row and field. Remove unsupported deductions, liabilities, net pay, or negative entries; correct malformed required data; then export and import a complete supported file. GrantLink does not import only part of a file.

A cost has no eligible grants

Confirm the correct Initiative, then check whether an active, date-eligible grant funds it. See Programs and Initiatives. Do not choose an unrelated grant simply to remove the unresolved amount.

A report stays Working

Open Needs attention to resolve work evidence and grant amounts. Then use Resolve QuickBooks matching from the Report view. You may preserve the current state as a Working snapshot, but its open items remain part of that snapshot.

The source run was replaced or voided

Import changed source content with the same run identifier as a revision. Ask GrantLink to void a run only when the payroll source itself was voided. Never delete or offset history with an invented negative row.

You are not sure what to do

Ask normal GrantLink chat: “What does payroll still need from me?” The assistant can read current payroll allocations and explain unresolved evidence, grant decisions, and QuickBooks matching without creating a parallel workflow.

Search docs

Type to search documentation pages and sections.