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 not whether Hashavshevet invoice scanning exists, but whether you want documents to move straight into the ERP or through a review layer first.

That distinction matters if you work in English, switch between English and Hebrew help content, or need more than a basic posting flow. Hashavshevet, also known in some contexts as H-ERP by Wizsoft, is a widely used Israeli ERP and accounting platform, so the choice matters to business owners, bookkeepers, and finance teams who already depend on it. Official pages now show that it has live invoice-capture options, but they do not really provide a practical English guide that explains which option fits which operating model.

If you are evaluating Hashavshevet OCR options, it helps to think in three paths. H-SCAN appears to be the native in-product route for scanning purchase documents into the Hashavshevet workflow. H-DOKKA appears to be the supplier-invoice automation route Hashavshevet now promotes alongside it. An extraction-first workflow sits before the ERP, gives you structured output, custom fields, and a review step, then lets you decide what should be imported.

That is a more useful framing for Israeli finance teams than the old assumption that Hashavshevet has no scanning. In simple terms, H-SCAN is the native in-ERP scanning path, H-DOKKA is the supplier-invoice capture path, and extraction-first means review and 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.

What H-SCAN Appears To Handle Inside Hashavshevet

Based on the official product and help pages cited in the brief, Hashavshevet H-SCAN is presented as the native path for scanning purchase documents inside the Hashavshevet environment. The public material points to a workflow where users submit purchase-document files, the system recognizes key invoice data, and the result feeds into the accounting process that Hashavshevet already expects.

The most useful operational detail comes from the help documentation rather than the marketing copy. It indicates support for PDF and image files, references Hebrew and English documents, and even mentions handwritten material. It also describes the output in accounting terms, including the creation of supplier invoice journal entries from scanned purchase documents. For teams specifically researching H-ERP invoice scanning, that is the clearest sign that H-SCAN is meant to stay close to the core ERP workflow rather than act as a generic export tool.

That closeness is also the main reason some teams will like it. If your goal is to scan invoices into Hashavshevet with as little workflow change as possible, a native module is naturally attractive. You are likely to prefer this route when your invoice formats are fairly predictable, your posting structure is already aligned to how Hashavshevet wants the data, and your team does not need a separate review layer in Excel or CSV before import.

In practical terms, H-SCAN is the best fit for teams that want invoice capture to stay inside Hashavshevet and do not need a separate review or export step before posting.

What H-DOKKA Adds For Supplier Invoice Capture

The second path now visible in the Hashavshevet ecosystem is Hashavshevet H-DOKKA. From the current product pages and support material referenced in the brief, this looks less like a basic scanning module and more like a dedicated workflow for Hashavshevet supplier invoice capture.

The capabilities described publicly are broader than simple document reading. Hashavshevet presents H-DOKKA as an OCR and AI-driven process for supplier invoices that can parse supplier details, capture VAT-related fields, archive documents digitally, and transfer the results into Hashavshevet. That framing matters because it suggests H-DOKKA is aimed at the intake and handling of supplier invoices as an operational process, not just at turning a document image into text.

That is the clearest difference from H-SCAN. H-SCAN appears centered on direct scanning and posting inside the ERP workflow. H-DOKKA appears centered on supplier-invoice automation, with more emphasis on invoice capture and document handling before the data lands in Hashavshevet. If your pain point is not just reading documents but reducing AP handling friction around incoming supplier invoices, H-DOKKA may be the stronger fit on the evidence currently available.

That makes H-DOKKA easier to place in the decision framework. If H-SCAN is the native in-ERP scanning route, H-DOKKA is the supplier-invoice capture route. Hashavshevet also sits in a wider ecosystem of third-party ingestion and export tools, so the real comparison is not native versus nothing. It is direct ERP capture versus how much review, mapping, and export control you want before posting. That is the more useful way to evaluate Hashavshevet invoice automation options.

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 invoice entry Hashavshevet workflows without giving up review and export control, that is a materially different proposition from direct posting.

The same export-first logic can matter beyond invoices. If your team also processes statements, receipts, or other mixed financial documents, an export-first layer often creates cleaner downstream data. Our article on processing Hebrew financial documents into spreadsheet-ready data shows why that matters in Israeli finance operations where document formats are rarely uniform.

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.

For Israeli SMB operators, the native route may be enough when the goal is simply to reduce repetitive entry work. For internal finance teams, the better question is often whether the workflow preserves the fields and review controls the month-end process actually needs. For bookkeepers and accountants handling multiple clients, the answer often shifts again because one fixed posting path rarely fits every supplier format.

That is the honest takeaway from the current market. Hashavshevet does have invoice scanning now, so the decision is no longer about filling a complete product gap. It is about deciding how much control you want over extraction, review, and import. 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.

In other words, start with the workflow you need, not the label on the feature page. That is the fastest way to choose between direct Hashavshevet invoice scanning, supplier-invoice automation, and a more flexible import-first setup.