The certificate that expired six months ago is still on the file.
Collect resale, SSUTA and multi-jurisdiction exemption certificates as part of the credit file, and let SCREDIT watch the expiry dates — so a lapse surfaces as a reminder rather than as an audit finding.
Nothing in a shared folder knows the date a certificate stops being good.
The certificate arrives as a reply to whoever asked for it. It is filed by whoever happened to notice. The exemption reason and the permit number stay inside the PDF, so nobody can answer a question about them without opening it. And the expiry date is written on a document no system is reading. The next time anyone looks is an audit, or a customer who has been invoiced without tax for a year on a certificate that lapsed in March.
What SCREDIT delivers
Ask for the Certificate You Actually Need
SCREDIT proposes the documents an application requires, so the tax certificate is requested as part of the credit file rather than remembered later. The request goes out with its own purpose-built wording, to the customer or to whoever at the customer is authorised to sign it.
Complete It Online, or Send What You Already Hold
The SSUTA and multi-jurisdiction certificates are fillable in the browser and route for signature. A customer who already holds a state or resale certificate uploads that instead. Both paths land in the same place, and neither asks the customer to do the work twice.
The Fields, Not Just the File
Certificate type and number, exemption reason, permit or registration number, effective and expiry dates are held as data alongside the document. Questions about a certificate get answered from the record instead of by opening the PDF. The tax ID is handled as sensitive throughout.
Reviewed Before It Counts
A submitted certificate goes to a person before it is accepted. Approve it, or send it back with what needs correcting. Nothing becomes the certificate of record because it merely arrived.
SCREDIT Watches the Date
A nightly sweep reads the expiry date on every certificate on file. Renewal reminders escalate on the schedule you set for that certificate type, each stage firing once rather than nightly, and they stop the moment the replacement arrives.
When One Lapses, Everything Using It Knows
A certificate does not just change its own status at expiry. Every application that was relying on it sees it go stale at the same moment — which is the difference between a document store and a system that knows what the document was for.
Asked Once, Not Every Order
A certificate already on file is reused rather than re-requested, and where a customer has sent more than one, the certificate that covers longest is the one that gets used. The chase stops because the answer is already there, not because someone remembered to check.
What changes on the desk
No Silent Lapse
The expiry date is read by something other than a person who remembers to look.
One Place the Certificate Lives
The document, its exemption reason, its permit number and its dates, on the credit file rather than in a thread.
The Renewal Chase Runs Itself
Reminders escalate, deduplicate, and stop on their own when the replacement lands.
The Customer Is Asked Once
A certificate on file is reused across the applications that need it.
Frequently asked questions
Which tax certificates can we collect through SCREDIT?
The SSUTA Certificate of Exemption and the uniform multi-jurisdiction certificate ship as completable, signable forms. Any other certificate your customer already holds — a state resale certificate, a state-specific exemption certificate — is collected as an upload against the same record, with the same fields and the same expiry monitoring. Exemption reasons such as resale, manufacturing, agricultural, government or nonprofit are captured as a field on the certificate rather than as separate document types, because that is how the certificates themselves are structured.
Does SCREDIT decide whether an exemption is valid?
No, and the distinction matters. SCREDIT collects the certificate, holds its details as structured data, routes it for human review, and monitors its expiry. It does not verify a certificate against a state registration database, and it does not determine whether a given transaction is taxable — that is your tax engine's job and, ultimately, your tax advisor's. What SCREDIT gives you is the certainty that the document exists, that someone looked at it, and that you will hear about it before it expires.
What actually happens on the day a certificate expires?
Before that day, renewal reminders go out on the schedule configured for that certificate type — thirty days and seven days ahead of expiry out of the box, adjustable per type. Each stage fires once, so a nightly sweep never turns into nightly email. On the day itself the certificate moves to expired, and every application that referenced it sees it stale simultaneously rather than one at a time as somebody opens them.
Whose certificate forms are these — yours or ours?
Yours. SCREDIT ships the SSUTA and multi-jurisdiction forms as templates in a standard pack that your business group installs, reviews and configures before use, the same way it handles any other document definition. They are a starting point that saves you building the field map, not legal paper supplied by EFILOS. Your own certificate forms can be added alongside them, versioned so that changing a form does not rewrite the history of certificates already signed against the old one. As with any tax document, the wording you put in front of a customer should be the wording your advisors have approved.
Do we have to ask for a new certificate on every order?
No. A valid certificate already on file is reused for the applications that need it rather than re-requested, and where a customer has provided several, the one covering longest is the one applied. The point of collecting a blanket certificate is that it covers future purchases, so a system that asks again on every order has thrown that away.
How does one certificate work for a customer buying into several states?
The SSUTA and multi-jurisdiction forms are structured per jurisdiction: each row carries the state, the customer's identification number there, and the exemption reason that applies in that state — because the same customer can claim different reasons in different places. SCREDIT holds the certificate and the jurisdictions it names as one record, with one expiry date to monitor. Where a state requires its own form instead, that certificate is collected alongside as a separate record.
Where do the certificates live, and who can see them?
On the credit file, in SCREDIT's own document platform, with role-based access and a record of who opened what. The tax ID and other sensitive fields are masked accordingly. The customer sees their own certificates and outstanding requests in the SCONNECT portal. Our security posture, and what we have and have not been audited against, is set out in full on the Trust Center.
Bring a certificate you currently keep in a folder.
We will send it out as a request, take it back through review, and show you what happens on the day it expires — including what it does to every application that was relying on it.