Evidence Layer — partner and embed program
The dated receipt, inside the software your users already open.
A county, a CPA firm, a pass-through agency and a bidder all owe the same small act: look at the official source before the money moves, and keep a dated record of what it printed. The Evidence Layer does that act from inside the binder, the vendor master, the bid portal or the grant file — automatically, every 30 days — and leaves the determination where the rule puts it: with the professional. We supply the record. We never represent anyone on an audit, and we never say "compliant".
Audit software — CPA firms
Single-audit CPA firms and the audit-binder tools they use (Caseware, Thomson Reuters, CCH, Suralink and in-house binders).
Duty documented: Compliance Supplement Part 3 §I — was SAM.gov checked before the award, and where is the dated record?
- One dated receipt per sampled vendor, pulled from inside the engagement binder; every non-answering source named
- Workpaper cover per engagement with hash, signature, RFC 3161 timestamp and transparency-log proof
- Client board as the Clearinghouse prints it: latest filing, 200.512 due date by rule, prior findings, repeat flags
- Audit Handover per client: five filing years threaded, CAP text as filed, for the incoming senior
Your users get: Hours off every S&D test; a reviewer can re-check any receipt without an account; the firm's name never appears on what we print.
How it starts: A firm sends one engagement's S&D sample as a CSV. Receipts and the workpaper cover come back within 48 hours. Then the embed.
AP / ERP — vendor master
Accounts-payable and ERP systems used by counties, districts, authorities and nonprofits (Tyler Munis, Sage Intacct, QuickBooks, MIP, Workday).
Duty documented: 2 CFR 200.214 / 180.300 and FAR 52.209-6 — the exclusion check on each vendor before a covered transaction, kept in the file.
- Every vendor in the master gets a dated receipt on entry and a re-read every 30 days, attached to the vendor record
- Changed lines since the last read, printed as the source printed them — never characterised
- SAM registration expiration as printed, beside the vendor
- A roster CSV the finance director can hand the auditor
Your users get: The vendor-file duty is done by the system, not by whoever remembers; the auditor's question has a dated answer in the record.
How it starts: One public body's vendor master, re-read monthly on invoice — the roster product — delivered through the partner's own screen.
Procurement portals — bid submission
Bid and solicitation portals (Bonfire, OpenGov Procurement, PlanetBids, BidNet, Periscope) and the offices that post on them.
Duty documented: The solicitation clause that asks each bidder for a dated record of what SAM.gov and the state lists printed for the bidder's exact name and UEI.
- Clause text as issued, with the packet address, pasted from the portal
- Bidder pulls a free receipt and attaches it at submission; it lands in the office board automatically
- Awardee read at award, dated, attached to the award file
- Office board exportable to CSV and a printable page for the procurement file
Your users get: The portal carries the proof format every county asks for; the office stops collecting PDFs by email.
How it starts: One office opens a Bid Packet at /bid/new and pastes the clause into its next solicitation. The portal link comes after.
Grant management — pass-through agencies
Grant-management platforms (eCivis, AmpliFund, Blackbaud Grantmaking, Fluxx) and state pass-through agencies monitoring subrecipients.
Duty documented: 2 CFR 200.332 subrecipient monitoring — a separate duty from the vendor exclusion check; the receipt supports the record of what the Clearinghouse and SAM printed for each subrecipient.
- Per subrecipient: the latest Single Audit filing as the FAC prints it, findings as filed, 200.512 due date by rule
- Audit Handover per subrecipient — five years threaded, CAP text, repeat indicators, no score
- SAM registration and exclusion rows as printed for the exact UEI
- A dated read when the subaward is made and again at each monitoring cycle
Your users get: The monitoring file shows what the official source said and when; the risk assessment stays the agency's.
How it starts: One agency's subrecipient list, read once as Handover files, on invoice. Then the embed in its grant platform.
Cooperative purchasing programs
Cooperative and piggyback programs whose members buy off awarded contracts (state cooperatives, Sourcewell, OMNIA, HGACBuy, BuyBoard).
Duty documented: Members still owe their own 2 CFR 180.300 / FAR 52.209-6 check when federal money pays — the cooperative's award does not do it for them.
- A dated receipt for each awarded vendor, re-read monthly, published to members beside the contract
- Member pulls the receipt into its own file at the moment of its purchase order
- Changed lines since last read, as printed
- A roster CSV per program for member auditors
Your users get: Members get the dated record without each of them building the check; the program never asserts eligibility — it publishes what the source printed.
How it starts: One program's awarded-vendor list as a roster, on invoice; members read it free.
What the layer never prints
- No compliance, eligibility, identity, risk or clearance determination — in the embed or anywhere else
- A source that does not answer is printed as "did not answer", never as "no record"
- No score, pass/fail, "clean" or ranking; nothing a partner pays changes a line
- Audit representation, audit opinions and legal advice are the licensed professional's work, not ours
- Hashes, signatures and the transparency log prove our capture; the agency remains the author of its record
Licence terms: attribution "Read by Alpha Covenant Holdings" on every embedded receipt; independent reads of public data are not ours to charge for. Printed prices · Trust and controls · Uptime standards.
How to start without building anything
Every track begins with a product that already ships on invoice: one engagement sample, one vendor master, one Bid Packet, one subrecipient list. The embed is built for the first partner's own tool after that order — not before. Get a dated quote