Skip to main content
Need help in this area? See Data Input FAQ.
Navigate to Data Input > Uploads and click any job row to view its details.

​
Job overview

The detail page displays:
  • Status badge — The current state of the upload job (Processing, Completed, or Failed).
  • Source — How the job was created (for example a normal upload or a Reprocess run).
  • Created time — When the upload was submitted.
  • Documents table — Every file in the job, with per-document status and results.

​
Documents table

Each row is one uploaded document (split pages from a merged PDF nest under their parent). Columns include: Use the row actions menu to open the bill, contest a duplicate, or start reprocess with feedback.

​
Results summary

Once processing completes, the results section summarizes outcomes in plain language — bills created, duplicates skipped, documents that were split, and similar.

​
Reprocess with feedback

When a document needs another pass (wrong dates, missed usage, incorrect site/account match, and similar), choose Reprocess with feedback from that document’s actions.
1

Open the dialog

On the documents table, open the actions menu for the document and select Reprocess with feedback. The action is available for processed, duplicate, error, non-utility, and demerged documents when Nectar still has a source file to re-run.
2

Add feedback

Describe what should change. Be specific — for example, which page has the correct usage table or which date field was misread. Feedback is required.
3

Optional site or account override

Leave site and account blank to keep the original matching behavior, or pick overrides so the new run targets a specific site or utility account.
4

Confirm

Submit to start a new upload job. The source document status becomes Reprocessed and links to that job. Any bill created from the document is deleted and replaced by the reprocessing result. For a merged document that was split into multiple bills, those bills are replaced together.
Follow the new job from Data Input > Uploads or via the link on the reprocessed document row.

​
Duplicates

If Nectar detects that an uploaded bill matches an existing record, it appears as a duplicate instead of creating a new bill. For each detected duplicate, you can:
  • Review the match to confirm it is truly a duplicate.
  • Contest the match if you believe the bill is unique and should be processed as a new record.
If you frequently upload bills that Nectar flags as duplicates, consider enabling Skip duplicate detection during the upload step.