Skip to main content

Importing a scheme from PDF

Written by Sven Poppelmann

Supported agreement PDFs can be processed into drafts for review. Available import types depend on enabled schemes and the farm; not every scheme document is supported.

Starting an import

  1. Open your farm's Schemes page.

  2. Choose Add Scheme > Upload agreements and add one PDF or several.

  3. Check each file's detected scheme type and use its offered dropdown to correct it where needed. The document content, not just the filename, determines detection.

  4. If the farm has no parcels, follow the offered land-setup or RPA-fetch step. This upload stays on the farm you are viewing.

  5. Click Process and monitor the upload window or the header's Jobs button for progress, review-ready drafts and errors.

Processing can extract and verify content, parse items, match land and assemble a draft. The exact statuses and stages depend on the import route. No fixed completion time or successful match is guaranteed.

Reviewing and saving

  1. Open the draft when ready for review.

  2. Compare the reference, name, dates, actions or options, capital items and parcel matches with the original PDF.

  3. Use the Agreement Details edit controls where offered, and correct supported fields or matches.

  4. Review the Import Warnings panel: it names warning types and affected items, and highlights relevant item rows. Resolve missing quantities, unsupported codes or unmatched land before saving, and complete any hectares confirmation.

  5. Save the agreement and check it appears correctly in Schemes. A normal, non-draft import attempts to generate work directly in the live Tasks list, without a task-confirmation queue. Task generation can fail independently of saving the agreement; check the generated work. A saved DRAFT creates no tasks until explicit activation. Review work and assignments after a live save or activation.

Hectares confirmation

Import saves for SFI, CS, SFS, AECS and IACS check for a recorded hectares confirmation. Existing legacy confirmation records satisfy the gate; it is not simply a rule for farms created after a particular date.

Where required, review the farm's land total against available imported agreement parcel areas. A difference greater than 2% needs a note when confirming. Outside-England skips are recorded automatically. An RPA-unreachable skip has an explicit recorded reason; do not assume a failed RPA connection silently bypasses the check.

Review low-confidence or unmatched land carefully. Cancel/discard controls can discard an unsaved draft; check the confirmation and job result. If processing fails, use the available retry or manual-entry route and verify the source document and resulting records. After saving, use Manage > View original document to compare the scheme with its source where available.

Save an agreement that is not in effect yet

Choose Save as draft in the upload window or review screen when the agreement is not ready to take effect. Review and save it as usual. The resulting agreement is marked DRAFT and starts no tasks, reminders or payments; it does not contribute to compliance or planning. This held agreement differs from an ordinary import's temporary extraction draft.

When ready, open Manage > Activate where permitted. Check the start and end dates against the original, tick the date-confirmation checkbox and select Activate agreement. Resolve listed problems with details, items or parcel links. Activation retains the same agreement, source document and assignments. A future start date does not activate a DRAFT automatically.

Uploading a revised agreement

On the individual import-review page, saving a document for an agreement the farm already holds opens Review the changes when changes are detected. Inspect agreement details, added or changed options, parcel assignments, rotation years and the payment schedule. Changes start ticked: untick anything that should stay as recorded, then use the displayed Save control. Already-paid years are kept. Items absent from the new document are shown but not automatically removed. Check the saved version against the issued document. Bulk approval, Ask and MCP import routes do not provide this same selective review; do not assume they apply only ticked changes.

Did this answer your question?