carbon ink

Invoice walkthrough

Follow an invoice from offline to NetSuite.

What happens after a rep submits with no signal? Follow one example through capture, local submission, reconnect, and the NetSuite result. Then use the same checks to test your own configured workflow in sandbox.

Explore the interactive example

Connor, Founder, Carbon InkUpdated 3 min read

Key takeaways

  • Offline capture uses data already synced to the Android device.
  • Submitting locally saves work for synchronization; it does not yet create a NetSuite record.
  • Reconnect lets the submission move through the configured integration.
  • Verify the resulting transaction before calling the workflow complete.

Follow the submission

One invoice. From device to office.

Interactive illustration · Fictional data

Explore the sequence below. This is a simplified example, not a product recording or a live NetSuite connection.

Step 1 of 4

Build the delivery invoice offline.

The customer and prices were synced before the route. The rep adds the delivered items while the device has no connection.

Android · Delivery invoice

Offline

Sample Market

Fictional customer · Wholesale pricing

  • Sparkling water · case12 × $18.00$216.00
  • Cold brew · case6 × $24.00$144.00
Subtotal as submitted$360.00

Draft on device

NetSuite · Example destination

No transaction received

The invoice is still on the device. NetSuite cannot receive it until connectivity returns and synchronization succeeds.

Example reference: DEMO-1042

What to check

See the difference between saved on the device, sent, and accepted in NetSuite.

A repeatable test

Use a sandbox customer and a small set of approved items, with expected prices recorded first.

Clear inputs

Check that customers, items, and pricing are available before disabling the connection.

A real offline check

Switch off Wi-Fi and mobile data on the test device before capturing the invoice.

Saved versus sent

Confirm local submission separately from the later connected processing step.

A result to inspect

Compare the final NetSuite record with the intended customer, items, and quantities.

A recovery check

Identify how your team finds and resolves submissions that need attention.

1. Prepare a small sandbox transaction

Choose an approved sandbox customer, two items with known prices, and a device your reps actually use. Confirm the destination transaction type before the test. Check that your sandbox scripts, emails, and integrations will handle test transactions appropriately.

Sign in while connected and complete the data sync. Open the customer and verify the needed items and prices. A device cannot fetch missing pricing or a new customer while offline.

2. Capture and submit without connectivity

Disable Wi-Fi and mobile data, then build the invoice. Confirm the customer, quantities, and prices before submitting. Carbon Ink saves submitted work locally for synchronization.

At this stage, NetSuite has not received that offline submission. Keep the device and app data intact until synchronization is confirmed. Closing and reopening the app can be part of the saved-work test; restarting the tablet is a separate access-recovery scenario.

3. Reconnect and inspect the destination record

Restore connectivity and check synchronization status. Processing time depends on the connection, integration, and NetSuite account. Do not use a fixed stopwatch target as a substitute for verifying the actual result.

Open the resulting NetSuite transaction and compare it with the submitted work. Check the customer, item quantities, pricing, transaction type, and any taxes or adjustments. Carbon Ink uses a stable submission identity to recognize retries; include an interrupted reconnect in your sandbox evaluation.

  • Verify the expected transaction exists in NetSuite.
  • Compare customer, items, quantities, and prices.
  • Review final taxes and any account-specific adjustments.
  • Check that a retry did not create an additional transaction.

4. Test the cases that interrupt a route

Repeat the exercise with missing pricing and an interrupted connection. Missing data should prompt a useful next step, rather than a guessed price or an assumption that the transaction reached NetSuite.

A NetSuite validation error may need an administrator to correct configuration before processing can succeed. Agree on who reviews exceptions, how the rep sees the current state, and when it is safe to continue. The interactive example illustrates the sequence; your sandbox test establishes whether your account is ready.

Good to know

  • The interactive example uses fictional data and simplified screens. It is not a recording, a live integration, or a timing benchmark.
  • Offline access is time-bounded. Initial sign-in, access renewal, and recovery after a tablet restart require connectivity.

Common questions

Is the interactive example connected to NetSuite?

No. It is a self-contained illustration using fictional data. It makes no invoice submissions and does not connect to an account. Use the written steps to run a controlled test in your own sandbox.

Does saved offline mean the office can already see it?

No. Work held only on a disconnected device is not yet available to the office. Synchronization must occur before remote systems can receive it.

What if NetSuite rejects the invoice?

Treat it as an exception to investigate. Check the validation or configuration issue with your administrator and confirm successful processing before considering the transaction complete.

Can we run this test with our own catalog?

Yes. Connect your sandbox, synchronize approved test data, and review the configured transaction workflow before performing the test on Android.

Run the test with your own catalog.

Start in sandbox, or walk through the offline and reconnect checks with the Carbon Ink team.