Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

Schedule electronic document processing

This page is for administrators who set up electronic documents. You set up job queue entries so documents are fetched, converted and sent automatically and errors reach you by e-mail.

Purpose

The system processes the documents at the times you choose, without a user doing it manually. Three job queue entries come with electronic documents:

Object IDObjectParameterWhat happens
10041560RdN eDoc BatchEmpty, or fetch, send, unimazestatusFetches, converts and sends documents and updates Unimaze statuses.
10041563RdN Create eDocsDate formula, default <-1D>Creates electronic documents for posted invoices that don't have one.
—Clearance jobCLEARDeletes old document data. Created from the setup, see Set up automatic data clearance. Don't create it manually.

Prerequisites

  • The delivery sites to process have Automatic Processing selected. The job queue skips other delivery sites.
  • E-mail is set up in BC if errors should be e-mailed.

Permissions

The user needs the EDOCS permission set and permission to create and start job queue entries in BC. The user who runs the entry also needs EDOCS.

Steps

Fetch, convert and send documents

  1. Open Job Queue Entries and create a new entry that runs object 10041560 (RdN eDoc Batch).

  2. Choose a parameter:

    • Empty: the system clears general errors, fetches documents, sends ready documents, converts all incoming documents to BC documents and updates Unimaze statuses, in that order.
    • fetch: fetches documents and converts them to BC documents, see Convert to BC document.
    • send: sends documents with the status To be sent, see Send an electronic invoice.
    • unimazestatus: updates the status of sent documents at Unimaze, see Unimaze message status. Unimaze Status From Date in the setup limits which documents are updated.

    The words are case-insensitive and can be combined, for example send;unimazestatus. If none of them is in the parameter, the run stops with this error:

    Invalid parameter: %1. Supported parameters are: fetch, send, unimazestatus. The Parameter is case-insensitive and can contain more than one trigger word.
    
  3. Choose the recurrence and run times and set the entry to Ready.

For example, run one entry with fetch every hour and another with send;unimazestatus every 15 minutes.

Create missing electronic documents

An electronic document is created as soon as an invoice is posted for a customer with a delivery site. This entry only catches invoices that were missed, for example posted before the delivery site was set on the customer or by a user without access to electronic documents.

  1. Create an entry that runs object 10041563 (RdN Create eDocs).
  2. In the parameter, enter how far back to look, for example <-7D>. An empty parameter means <-1D>. If the minus is missing, the system still looks back in time.
  3. Choose a recurrence, for example daily, and set the entry to Ready.

The entry goes through all customers with a Delivery Site and creates an electronic document with the status To be sent for posted sales and service invoices and credit memos in the period that don't have one. The next run with send sends them.

E-mail errors

  1. Open eDoc Setup and go to the Errors group.
  2. Select Send Error Email and enter addresses in Error Email Recipients. An invalid address stops the run.

After each run of 10041560, the system sends an e-mail if general errors occurred, that is errors that don't belong to a single document, for example connection errors. The subject is %1 errors found in eDocs. If there are no such errors, no e-mail is sent. The e-mail uses the RdN eDocs e-mail scenario.

Schedule electronic document processing in Business Central

Verify

  • Open the job queue entry after the first run and check the status and errors.
  • Open the eDoc worksheet and check that new documents were fetched or sent.
  • If nothing happens, check Automatic Processing on the delivery site and errors. See also Help.