VAT4U now connects directly to Rydoo. Once your Rydoo credentials are registered, reported expenses are pulled automatically for a chosen export period and handed to the import wizard, exactly like the existing Yokoy and Expensya connectors.

Two refinements followed shortly after launch. Extractions now recognise expenses that were already pulled in an earlier run, so overlapping or re-run date ranges no longer create duplicates, and the connection itself is more resilient over long extractions.

Companies can now connect a Microsoft 365 tenant and register one or more SharePoint lists that hold their expense documents. You continue to upload your own expense data as a CSV, and SharePoint supplies the matching supporting documents.

Each row carries an Expense ID, and every configured list is searched for it during document retrieval. When a receipt is spread across several pages or several lists, all the pages found are merged into a single document.

The Concur bidirectional dashboard has been rebuilt around a work queue: every report that still needs attention is placed in exactly one action section, so it is immediately clear what to do next rather than what merely happened. Insights sit alongside it for the wider picture.

Each section header now shows how many expenses it covers, not only how many reports, and that count links straight through to Manage Expenses pre-filtered to those exact expenses. Sections are sorted and paginated on the server, so large queues stay fast.

A Concur extraction now reports a distinct Transforming stage while the CSV files are being written. Previously a pull stayed on Processing until the very end and was marked finished slightly too early, which briefly revealed an empty file list. You can now tell a queue that is still retrieving reports from one that is already producing output.

A new batch action in Manage Expenses, Retrieve missing documents, fetches expense documents that a connector import never downloaded — for everything you have selected or filtered. Until now these expenses could only be recovered one by one with help from support.

Two situations create them: an import run without document processing, and an import that skipped documents for expenses that landed as excluded. Once the exclusion is lifted, the document is still missing. The action works out what each expense needs, shows you a preview of exactly what it will do before anything happens, and afterwards reports every expense it could not queue together with the reason why.

Connectors, SFTP drops and imports that hand VAT4U a ZIP of scans, a Word or Excel receipt, or an .msg / .eml email or even iPhone specific image format - HEIC - used to fail with "File format is not acceptable", leaving the expense without a copy. Those formats are now accepted and stored against the expense.

Some remote systems serve a document as an untyped binary. VAT4U used to reject these outright; it now inspects the content and recovers the document, so fewer receipts go missing during retrieval.

The look-ups behind the Expense Wizard's document panel, the import Documents tab and the per-import retry have been reworked. Screens that touch remote documents open noticeably faster, and large retrieval runs that used to time out now complete.

Identify car repair type distinguishes labour from parts on a vehicle repair invoice — the distinction several countries apply different recovery rules to. Identify UK VAT number and Identify Australian ABN number extract those identifiers where the standard VAT number field does not apply.

All three appear in the Smart AI modal alongside the existing assistants. Their answers become columns in Manage Expenses under AI Assistant & Human Review, where they can be filtered — including a Not analysed option — and are included in the expenses export.

Multiple accuracy improvements have been delivered across the SmartAI pipeline. Smart AI no longer produces phantom "Zero rated expense" lines with every amount at zero, including when a previously cached result is reused. Separately, the improvement to OCR layout now improves field accuracy across all document types.

In the Smart AI results screen, choosing Display only expenses from my current filterscorrectly re-scoped the counters but not the preview behind them — a field showing three differences could open a list of ten. The preview now honours the same scope as the numbers you clicked.

VAT4U now reads Mexican CFDI (SAT) e-invoices, extracting issuer and recipient details, line items, the tax breakdown, totals and the fiscal stamp. Alongside parsing, a validation pass checks the SAT Anexo 20 required fields and reports anything missing.

Mexico joins the formats VAT4U already supports: ZUGFeRD and Factur-X, XRechnung and PEPPOL BIS 3, Romanian e-Factura, Italian FatturaPA and Polish KSeF — including all of these embedded inside a hybrid PDF.

A non-EU applicant claiming from Belgium previously had no downloadable output. The Submission tab now offers Download BE 13th directive Excel, in line with the other country outputs.

Booking a claim decision now accepts a total approved amount higher than the amount claimed. Tax authorities do occasionally grant more than was asked for, and that outcome can now be recorded as it happened.

Two long-standing problems in claim post-processing have been fixed. An expense removed from a claim while the claim was still being processed could be silently put back into it, inflating the claim's expense count. And a claim processed twice in quick succession could end up with two orders. Processing now runs once at a time per claim and only ever touches expenses that are genuinely still members. Large claims also complete substantially faster as a result.

The public API reference has moved to developers.vat4u.com, generated from the API specification itself so it always matches what the API actually does. Every endpoint now carries a proper description, worked examples and full response schemas, including the new claim creation and submission endpoints.

Claim submission was previously available only in the interface. It can now be driven end to end through the public API, starting with French 8th Directive claims. Partners can initiate a submission, poll its progress, and respond to two-factor and captcha challenges without a person watching the screen.

Submission is asynchronous, portal credentials supplied inline are handled safely, bank details are validated before anything is sent, and new webhook events tell you when a submission changes status. More claim flows will follow.

The expense creation endpoint accepts a purchase-order reference and a bookkeeping reference on each individual line item, and returns them on retrieval. Your own ERP references now travel through VAT4U end to end.

A company can now be deleted through the API, mirroring the action available in the interface. The company and its data stop appearing in listings while remaining recoverable by support.

A share icon in the Manage Expenses toolbar copies the current page link to your clipboard, carrying your active filters and columns with it. Colleagues open precisely the same scope you are seeing.

The CSV and Excel import accepts two additional per-item columns, Item ERP Tax Key and Item ERP GL Account Number, validated against the tax keys and GL accounts configured for your company. Styled Excel files no longer break the import either.

In the expense wizard, excluding an expense from a draft claim used to re-link it and flip it back to claimed. Saving and excluding is now a single action, and the expense stays excluded.

Recurring invoice lines are now set up in the Pricing module, in a new Recurring invoice items section, instead of being fixed in a script. Each line defines its description, billing company, unit price, quantity, currency, VAT rate and issue schedule, with monthly, quarterly and yearly cycles supported and a preview before anything is issued.

The Invoices table has an editable Paid date column, which can also be cleared again once set. The Orders table has a Remittance Claim column, and where automatic e-invoicing is enabled, "Mark invoice as prepaid" is now ticked by default only for orders flagged as a remittance claim.

Credit notes are now issued with the correct e-invoice document type and positive amounts, and the invoicing Excel export shows credit note amounts with the right sign.

The IOSS transaction import accepts a standalone Customs fee column — a flat EUR tariff that sits outside the taxable base and is stored exactly as provided. Customs fee and customs duty totals are also kept on the return itself and shown in the return details, so the figures stay available after the transactions are filed.

Travellers now sign in to the VAT4U Travel app with a one-time code sent to their email address, with no password to remember or reset. Travellers can also provision their own account, so rolling the app out across a company no longer requires creating every user up front. Password sign-in remains available as a fallback.

Travellers can upload a profile picture from the app, which appears wherever their account is shown in VAT4U.

The background jobs table has a Created at column that can be filtered by date range, and the Job ID column has been replaced by a search box with a copy action. Unusual filter or sort combinations no longer break the list.

Demo companies are now cleaned up automatically 30 days after their last activity, with a reminder emailed to whoever created them beforehand. Activity counts claims and company changes as well as expenses, so a demo that is genuinely in use is not removed — and the reminder reaches its creator even if they no longer hold a role in that company.

Claims and expenses belonging to a deleted company no longer appear to representative and batch-processor users in Manage Claims and Manage Expenses.

Moving a file in the SFTP browser now explains why a move failed — most often a file of the same name already in the destination — instead of a generic failure. And a default description language configured in an import mapping is applied as intended rather than silently dropped.