SR SOFT LLC is an E-Verify Company

← Journal

SAP Vertex × FICO

SAP Vertex Indirect Tax: Nexus, Jurisdiction, and the Processes That Break Close

  • SAP Vertex
  • Nexus
  • Sales and use tax
  • Home-rule
  • Exemption certificate
Documents
Jurisdiction is a stack of paper until Vertex makes it a call.

Indirect tax in the United States is not a rate table. It is economic nexus after Wayfair, origin versus destination, home-rule cities, special districts, product taxability, bundled software, SaaS, freight, and a certificate vault. Vertex exists because SAP condition technique cannot keep that statute book current. Integrating it into FICO is where implementations become folklore.

A marketplace facilitator, a seller of record, and a drop-ship supplier are three different taxpayers on a single customer order. Digital goods taxability changes by state and by year. Construction and job-site ship-to is not a customer master. Returns and credit memos must reverse the original jurisdiction, not re-determine on today’s address. Tax-only invoices and statistical conditions in pricing will fool a junior tester and fail an auditor.

NexusJurisdictionExemptionCertificateReturnDetermination graph
Determination graph we walk in design: nexus, jurisdiction, exemption, certificate, return
SalesQuoteCert askOrderTaxValidateExpireJob-siteVertexExemptRateDocRTRExtractReturnNotice
Certificate and return calendar — the half nobody staffs

Nexus is a legal fact with a system shape

Physical nexus, economic nexus, click-through, inventory in a 3PL — legal decides. The system must stop charging where you have no nexus and start the day you do. SR Soft writes the nexus matrix with tax counsel, not with a developer guessing from a rate file. We test the day nexus flips. We test the home-rule city that is not the state.

Freight yard
Freight taxability is a logistics fact. The incoterm is the requirement.

How SR Soft handles the graph

We staff Vertex configuration, SAP pricing, and FICO tax accounts as one motion. We write the nexus matrix with tax. We test returns. We test credit memos. We test the expired certificate. Fortune 500 operators who cannot miss a filing buy this because a notice is more expensive than a cell. AI for certificate anomaly detection is on our roadmap; unattended exemption is not.

  1. 01

    Product taxability catalog

    SKU families mapped to Vertex categories legal will own.

  2. 02

    Nexus calendar

    Effective dates, not a flag.

  3. 03

    Partner-function matrix

    Ship-to, ship-from, sold-to, title.

  4. 04

    Certificate process

    Vault, expiry, job-site, blanket.

  5. 05

    Return extract

    G/L to Vertex to filing. Recon owner named.

  6. 06

    Notice path

    Who gets the letter. Who opens the document.

Determination design we refuse to skip

Filing exceptions (index)

After certificate vault and nexus matrix are owned

Home-rule, nexus flips, and the certificate that expired on Tuesday

A home-rule city is not the state. Economic nexus after Wayfair is a calendar, not a flag. A job-site ship-to is not the sold-to. A blanket exemption that expired is a taxable document, not a warning in a log. Marketplace facilitator versus seller of record changes who Vertex thinks the taxpayer is. If your determination design cannot express those sentences, you will file the wrong return with perfect confidence.

noyesvalidexpiredOrderNexus?Cert valid?No taxDeterminePost / file
Exemption and nexus decision inside a single order

Digital goods, SaaS, and bundled software change taxability by state and by year. Freight follows the incoterm and sometimes the statute, not the access sequence you copied from the last client. We keep a product-taxability catalog legal owns. Vertex categories are not invented by the developer who mapped “MISC.” Returns clone original jurisdictions. Notices have a named path. That is the process. The software is the calculator.

Pinned map
Nexus is a map with dates. A rate file is not a map.