Sales tax and VAT software for Priority ERP

Yes, in two places. In Israel, Priority connects to the Tax Authority's digital services and transmits each qualifying invoice to obtain an allocation number, which then prints on the invoice and is reported in PCN874. It also holds a pool of emergency allocation numbers for when the Tax Authority's systems are unreachable, and lets you send those invoices again once they are back. In the UK, Priority states that from version 19.0 it calculates and reports VAT to HMRC in the Making Tax Digital format, and its localization table marks that HMRC recognised. Neither of those covers a US sales tax return, and Commenda handles all 50 states plus 70+ countries from one filing calendar.

No, and Priority says so plainly. Its US Localization Map, updated in June 2026, answers sales tax with a single item: integration with Avalara AvaTax. Priority states that the integration is built in from version 19.1, that you need an active Avalara account with your own account number, licence key, and company code, and that you need the USA Module in your licence. Priority also states that it supports working with Avalara when the end customers are located in the US or Canada, and that for Canadian customers you must record tax groups and tax codes manually. Commenda maintains state, county, city, and district rates and applies them to the transactions already in Priority, with no separate engine to license.

The job changes, and so does the rate. In Israel your obligation is transaction-level: transmit the invoice, get an allocation number, report it in PCN874. In the US the obligation starts earlier and lasts longer. You have to work out which states you have crossed a threshold in, register in each one, collect at a rate that varies by state, county, city, and district, file on that state's frequency, and remit separately. Commenda does all of that from your Priority data, in all 50 states, and tracks exposure in 70+ countries so the EU side does not surprise you either.

No. Priority's Avalara procedure lists your nexus jurisdictions as a working assumption: you are expected to have defined your company and each subsidiary, and the jurisdictions with nexus, in the Avalara Admin Console before you begin. That is a declaration, not a measurement. Commenda measures the same Priority transactions against economic and physical thresholds in all 50 states, every EU member state, and 70+ countries, and notifies you at 80% of a registration threshold, before you cross it.

More than one field. Priority's own guidance was to open a new tax rate line in each of the output VAT, input VAT, and input VAT on assets rows, with a from-date of 1 January 2025 and 18% for both sales and purchases, then repeat it for any additional tax codes and for every tax group other than the exempt one, and then do all of it again in every active company in the system. The vendor's Hebrew title for that procedure is straightforward about what it is: an update to the VAT percentage. Commenda maintains rates centrally, so a rate change is not a configuration job.

Through country localizations, and what you get is local registers and reports. Priority's table covers 24 countries and a shared row for other European countries with a VAT report generator. Individual localizations name real local requirements: SII integration and Modelos 303, 390, 111, 347 and 349 for Spain, split payments and Esterometro for Italy, SAF-T for Portugal and Romania, VAT declarations and registers for Bulgaria and Slovenia. The EU row adds Intrastat, EC sales, the reverse charge scheme, and VIES verification. Commenda covers VAT, GST, and sales tax across 70+ countries, including EU VAT with OSS and IOSS, and files rather than reports.

It stores a reason. The certificate itself sits outside Priority. Priority's procedure has you run a program to retrieve exemption reasons from Avalara, then select one in an Avalara exemption code field on the customer's financial parameters. For a one-off exemption you put a value in the customer reference field on the sales document instead. Getting the certificate, checking it is valid, and noticing when it expires all sit outside Priority. Commenda collects them through a self-service portal, validates each one at upload, applies it automatically in the states where it is valid, and chases expiries.

Yes, and Priority already treats them separately. Its Israeli allocation setup is run per subsidiary, its Avalara credentials are recorded per subsidiary company code, and its consolidated business number field exists for companies that report an annual VAT return as a group. Commenda keeps a registration footprint, an exposure position, and a filing calendar per entity, so a threshold crossed by one subsidiary is never netted against another.