Sales tax and VAT software for JD Edwards

Only from rates you supply. In JD Edwards a tax rate/area is a code you set up, and the rate is a percentage entered as a whole number rather than a decimal, one line per tax authority and up to five per area, each with an effective and an expiration date. Oracle's documented route for US and Canadian rates is Vertex Sales Tax Q Series: it states that the U.S. and Canada tax authorities are stored in Vertex, and that Vertex compiles the GeoCode from state, city, zip code, and county and maintains the rates behind it. Commenda maintains state, county, city, and district rates and applies them to the transactions already in your JD Edwards ledger, so no correctness depends on a table somebody kept current by hand.

No. Oracle's localization list covers 34 countries and the United States is not one of them. What JD Edwards gives you in the US is reporting: a Tax Detail/Summary report, a Sales Tax report, a GST/PST report, and a tax reconciliation repository you update and then review against your general ledger accounts. Even with Vertex in place, returns are a separate purchase, and Oracle describes that Returns module as automating the preparation of state and local tax returns. Commenda files across all 50 states on each state's required frequency, tracks remittance per jurisdiction, and files amended returns where a period needs correcting.

It matters for scoping. It does not change whether this works. Commenda reads your transactions rather than replacing your tax setup, so your tax rate/areas, your tax rules by company, and your automatic accounting instructions stay exactly as they are. That is also why the mapping gets scoped rather than assumed. Oracle's own tax considerations page asks you to settle any special dispensations you have arranged with state or local jurisdictions, how your products fit into tax categories, how customers and suppliers are categorised, and whether returns are filed for one company or several. Those answers are specific to your install, and they are the first thing we go through.

No. Oracle states that Premier Support for JD Edwards EnterpriseOne 9.2 is available through at least 2037, on premises or on Oracle Cloud Infrastructure, and that new features arrive as updates to the existing 9.2 release rather than an upgrade. Commenda sits beside JD Edwards rather than inside its tax engine, so your registrations, your exposure history, and your filed returns do not depend on your release level or on when you next take an update.

Through country localizations, and the output is usually a file you submit. Oracle lists localizations for 34 countries across EMEA, LATAM, and Asia Pacific. Its generic VAT reports build an XML data set that BI Publisher turns into a localized report, and Oracle names four localizations that use it. For the OECD audit file, Oracle states that you may need to modify the delivered template to accommodate additional country-specific requirements before submitting it to your tax authority. For Poland it recommends integration with certified third-party providers to transmit e-invoices to the KSeF platform. Commenda covers VAT, GST, and sales tax across 70+ countries from one platform, including EU VAT with OSS and IOSS.

Because the interface recognises three of them. Oracle documents twelve tax explanation codes in JD Edwards, held in user-defined code table 00/EX, and each one specifies a different algorithm for how tax is assessed and how it is distributed to the general ledger. With Vertex Sales Tax Q Series switched on, Oracle states the interface recognizes only tax codes E, S, and U. It also notes that procurement and payables transactions carrying code S are not written to the Vertex tax register. Commenda reads the posted transaction and the tax on it, so what a code did upstream is recorded rather than reinterpreted.

No. Oracle's Tax Processing guide covers calculating tax, printing tax reports, validating tax IDs against VIES, and reconciling tax amounts to general ledger accounts. Measuring your sales in a state against that state's registration threshold is not part of it, and a tax rate/area carries an effective date rather than a threshold. Commenda measures the same JD Edwards 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.

Each entity is treated separately, and rolled up only where you want a group view. JD Edwards already works this way: tax rules are defined by company, tax authorities are set up per tax area, and Oracle's tax considerations page asks you to decide whether tax returns are filed for one company or for multiple companies. Commenda keeps a registration footprint, an exposure position, and a filing calendar per entity, so a threshold crossed by one company is never netted against another.