Nanonets in Structured Document Extraction

Nanonets passed this single-field extraction task. The receipt number appeared once on the document and returned as RHS-70234 in both the preview table and exported JSON; the other returned fields also matched the document.

Nanonets derived the requested value from the two present inputs and returned 81 for total_fuel_cost. The two operand rows carried source-link icons in the screenshot and the total row did not, matching the JSON output and showing the value as a computed field.

Nanonets chose the consignment reference, not the invoice number, for this field. The result row and exported JSON both show CFS-CN-40821, matching the supplied definition.

Nanonets passed this lookalike-row scenario. It returned five genuine line items and left out the lookalike Total row; the input table shows that row in the same layout, and the output has no 'Total' entry or 1,982 amount.

Nanonets kept one array across the page break. The output has ten objects in one top-level array, with no second array and no repeated member at the boundary. The invoice shows items 1-6 on page 1 and 7-10 on page 2, and the result screen shows the same single table numbered 1 to 10.

Nanonets returned the empty set the document called for. The input says no damage or exceptions were reported, and the output is an empty array; the capture shows the same field as List [0] with no rows.

Nanonets handled the mixed digital-and-scanned document in this test. It returned the five requested values, including the two that appear only in the scanned page image, and kept the digital-page values unchanged. The JSON output itself does not show per-value page provenance.

Nanonets returned the matching documents for the tested cross-document filter. It produced the two receipts above $150 and left out the one below that threshold. The screenshot also shows a Data Extraction step over three files before the final JSON answer.

Nanonets presented a document answer as extracted data without distinguishing its source. The first request correctly returned the receipt number, subtotal, tax and total due. The follow-up used the same extraction tool, placing the technician in a separate, similarly styled extraction block; the numbered source chip appeared only in the answer text below, which did not say the technician was outside the requested fields.

Nanonets passes this scenario. In the tested case, the corrected receipt number appears in the product’s delivery path: the result grid shows RHS-99999, the Download menu is open on that grid, and the exported JSON carries RHS-99999 with the other receipt values.

Nanonets let a user add one line item and remove another while preserving the other two rows. Both corrections persisted after a full page reload and appeared in the JSON export.

Nanonets traced the returned subtotal to page 2, where GBP 6,103.00 is highlighted in the totals block. The exported page number was 2, and the preview highlight sat on the returned value rather than the neighboring totals.