Reference · built on requestOperator by FibricFinance & billing

Tax Exemption

Tax-exempt orders checked against the certificate on file, its jurisdiction, and its expiry, with tax or a certificate request proposed.

About

An order marked tax exempt is a claim. The proof is a certificate: signed, covering the ship-to state, and not expired. This operator reads exempt orders from your store or ledger, looks up the customer's certificates in your tax engine or the folder where you keep them, and checks the three things an auditor will check.

When a certificate covers the order, it records the match. When none does, it proposes charging tax on the order or, where the customer is likely exempt, a request for the certificate. When a certificate is about to expire, it proposes the renewal request early. Each proposal waits for approval and leaves a record naming the certificate.

This is a reference listing. It documents what Fibric would read from Tax Exemption and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shopify orders and customers with tax_exempt true, and the tax_exemptions codes set on the customer
  • Customers marked exempt in BigCommerce, and Magento customers assigned to a tax-exempt customer group
  • AvaTax certificates for the company: signedDate, expirationDate, exposureZone, exemptionReason, valid, and status
  • TaxJar customers with exemption_type wholesale, government, or other, and the exempt_regions they cover
  • Certificate files in a Google Drive or SharePoint folder named by customer, with the file's modified date
  • The ship-to state or province on each exempt order, compared with the zone the certificate covers
  • Certificates within the notice period you set before their expirationDate

Proposed actions

  • Target capability: propose charging tax on an order whose ship-to state no valid certificate covers
  • Target capability: propose a certificate request to the customer by email, naming the state and the reason code required
  • Target capability: propose recording a received certificate in AvaTax with its signedDate, expirationDate, and exposureZone, linked to the customer
  • Target capability: propose setting a TaxJar customer's exemption_type and exempt_regions to match the certificate on file
  • Target capability: propose removing exempt status from a customer whose only certificate has expired or been revoked

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Every exempt order has a certificate behind it

    Shopify orders with tax_exempt true are checked against valid AvaTax certificates for the customer and ship-to exposureZone. Orders without cover are proposed for tax.

    With Shopify, Avalara AvaTax

  • Renew before it lapses

    Certificates inside the notice period before expirationDate trigger a renewal request through Amazon SES, proposed to the tax lead with the customer's open orders shown.

    With Avalara AvaTax, Amazon Simple Email Service

  • Keep TaxJar in step with the file

    When a certificate arrives in the SharePoint folder, it proposes setting exemption_type and exempt_regions on the TaxJar customer so future calculations exempt the right states.

    With Microsoft SharePoint, TaxJar

  • Exempt groups in Magento and BigCommerce

    Customers in an exempt group with no certificate on file are listed with their recent orders, and a request through Twilio SendGrid is proposed for each before the next order ships.

    With Magento, BigCommerce, Twilio SendGrid

Requirements

  • A commerce or ledger connector exposing the exempt flag on orders and customers: Shopify, BigCommerce, Magento, NetSuite, or Business Central
  • A certificate store: Avalara AvaTax, TaxJar, or a Google Drive or SharePoint folder with one file per customer
  • An email connector for certificate requests: Amazon SES or Twilio SendGrid
  • A notice period before expiry, and a rule for orders shipping to a state the certificate does not cover
Authentication
It has no tax-engine login of its own. Orders, certificates, and files are read through the commerce, tax, and file connectors you attach with the scopes you grant.

Limits

  • It checks presence, jurisdiction, and dates as recorded. It does not judge whether a certificate satisfies a state's law.
  • Where a store cannot re-tax an order already placed, the tax is proposed as an adjustment on the next invoice instead.
  • It does not calculate, file, or remit tax. Your tax engine does that; this operator asks whether the exemption was earned.
  • A certificate kept as an image only is matched by customer and filename. Its dates come from the folder, not the page.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Tax Exemption ↗

Questions and answers

What does the tax lead approve?
Each tax charge, certificate request, or certificate record is its own proposal. It shows the order, the ship-to state, the certificates found with their dates, and why none applies. Approve it, attach a certificate you already hold, or decline.
What record is kept for an audit?
A receipt per order or certificate: the certificate matched or missing, the state, the action proposed, who approved, and when. Certificates recorded through it carry the file they came from.
Does it change a customer's tax status by itself?
No. Exempt status is only removed or added after approval, once. Orders keep their original tax until a person approves the change.
Ask about Tax Exemption

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.