Hashavshevet Invoice Scanning: H-SCAN vs H-DOKKA

Yes, Hashavshevet now supports invoice scanning through H-SCAN and also promotes H-DOKKA for supplier invoice capture. For most teams, the real question is whether documents should move straight into the ERP or through a review layer first.

Hashavshevet is also referred to as H-ERP by Wizsoft, so English-language searches often mix product names, Hebrew help pages, and reseller material. Think of the choice as three paths: H-SCAN for native in-ERP scanning, H-DOKKA for supplier-invoice capture, and an extraction-first workflow when you need review, custom fields, and structured export before import. A bookkeeper with standardized supplier invoices may prefer the shortest path into the ERP. A firm handling mixed Hebrew and English documents, line items, or client-specific fields may want tighter control before anything is posted.

H-SCAN vs H-DOKKA Inside Hashavshevet

Hashavshevet's public product and help pages present Hashavshevet H-SCAN as the native path for scanning purchase documents inside the ERP. The help material indicates support for PDF and image files, references Hebrew and English documents, and describes accounting output such as supplier invoice journal entries from scanned purchase documents. For teams researching H-ERP invoice scanning, that places H-SCAN close to the core posting workflow rather than a generic export tool.

Hashavshevet's public H-DOKKA material presents it as a supplier-invoice capture workflow rather than a basic scanning module. The pages describe OCR and AI-driven processing for supplier invoices, including supplier details, VAT-related fields, digital archiving, and transfer into Hashavshevet.

In practical terms, use H-SCAN when you want to scan invoices into Hashavshevet with minimal workflow change and no separate review step. Consider H-DOKKA when the bigger problem is supplier-invoice intake and document handling before the data lands in Hashavshevet.

Both routes can reduce manual keying; the difference is how much control your team keeps before posting.

When An Extraction-First Workflow Is The Better Fit

If your team needs more than direct posting, an extraction-first workflow is often the safer choice. This is especially true when you need custom fields, line-item extraction, spreadsheet review before import, or one consistent structure across suppliers that all send different invoice layouts.

It is also where Hebrew invoice OCR for Hashavshevet becomes a practical workflow question rather than a pure recognition question. Right-to-left documents, mixed Hebrew and English invoices, and supplier-specific labels can all increase the value of reviewing extracted fields before they hit the ERP. Instead of pushing data directly into Hashavshevet and fixing issues afterward, you standardize the output first and only then import invoices into Hashavshevet in the format your team actually wants.

That approach is not anti-Hashavshevet. It is simply a different control point. A bookkeeping firm, for example, may want invoice number, supplier legal name, VAT amount, line items, cost center, and a client reference column checked in a spreadsheet before posting. That is hard to do well if the workflow assumes immediate entry into the ERP. It is much easier when the extraction step outputs structured Excel or CSV data that can be reviewed, filtered, and mapped first. A typical handoff looks like this: extract the invoice data into a structured file, review and map the columns your team needs, then run the cleaned result through your normal Hashavshevet import or posting process.

This is where an extraction-first tool such as Invoice Data Extraction can fit. Teams can upload PDFs, JPGs, or PNGs, tell the AI exactly what fields to capture, and download structured Excel, CSV, or JSON output. It can extract line items, preserve source file and page references for verification, and handle major languages and scripts including Hebrew right-to-left documents. If you need to automate Hashavshevet invoice-entry workflows without giving up review and export control, that is a materially different proposition from direct posting.

Which Invoice Fields And Compliance Checks Should Be Verified Before Import

Whatever capture route you choose, the real test is whether the extracted data is usable without cleanup. For most teams, that means verifying supplier identity details, invoice number, invoice date, tax date where relevant, net amount, VAT amount, total amount, and any reference values needed for audit trails or posting logic before anything is approved or imported.

That is why invoice capture in Israel is not just a speed problem. It is a field-quality problem. If the workflow misses or misplaces the data points that downstream bookkeeping depends on, you still end up doing manual correction work. Our guide to the invoice fields Israeli VAT compliance depends on shows why small extraction errors can turn into real VAT and bookkeeping issues later.

The same applies to qualifying invoices that sit inside Israel's SHAAM allocation-number workflow. According to OECD's 2025 note on Israel's invoice allocation system, Israel's Tax Authority system automatically adds 50,000 to 100,000 allocation numbers to invoices per day, with response times that do not exceed half a second. For a Hashavshevet team, the practical lesson is simple: the capture method has to preserve the right VAT, supplier, and invoice-reference fields before import, because the workflow it supports is real-time and detail-sensitive.

How Israeli Hashavshevet Teams Should Choose The Right Workflow

The best option depends on what you are trying to control.

• Choose H-SCAN if your team wants the most direct route inside Hashavshevet, your supplier invoices are relatively standardized, and you are comfortable with a native ERP-first process.
• Choose H-DOKKA if your priority is supplier-invoice intake and document handling, and the public feature set aligns with how your AP workflow already operates.
• Choose an extraction-first workflow if you need custom fields, line items, mixed document handling, bilingual review, or a spreadsheet checkpoint before import.

Hashavshevet does have invoice scanning now, so the decision is no longer about filling a complete product gap, and teams running Priority ERP face a similar vendor-neutral scanning decision with comparable trade-offs. Start with the control point you need. If your team needs structured export, custom fields, and a verification step before posting, adding invoice data extraction software for Hashavshevet workflows to the process can be the more practical route.