Cattle, Bison and Buffalo

This section outlines the steps required to successfully record livestock movements between two holdings within England using the Livestock Information Service.

It also allows an English keeper to report a movement to a holding in Scotland or Wales, this process is still under review.

Types of Movements

The various types of livestock movements and how the service manages them are detailed below.

Key Points

• Double-Ended Movements: This service requires both the sending and destination locations to be specified.
• Single Movement Entry: Only one movement entry is accepted, which must be confirmed by the receiving party. Duplicate entries from the other party are not permitted, as they create more than one movement reference for the same movement.

Process

Movements can be recorded by either the sender or the receiver:

Movements are entered as either Sending (if reported by the Sender) or Receiving (if reported by the Receiver).  Whoever reports the movement first creates the initial record, the other party will then have the option to review and confirm the movement.  For more information go to the Movement Review section below.

Pre & Post Movement

Species-Specific Movement Reporting Rules

Different species have different rules for when movements must be recorded in our service:

• Pre-Move Reporting: Some species require movements to be reported before the animals are moved.
• Post-Move Reporting: Others require reporting after or on the day of the move.
• Flexible Reporting: For certain species, including cattle, bison, and buffalo, movements can be reported either pre-move or post-move.

Reporting for Cattle, Bison, and Buffalo:

We accept both pre-movement and post-movement reports for cattle, bison, and buffalo. If you choose to implement pre-movement reporting, you must confirm the pre-movement has occurred. Please review the section on confirming pre-movements for further details.

For pre movement the other party will have the ability to reject the movement (or do nothing at this point) (see reviewing movement section).

Notification Process

• Notification Trigger: Both pre-move and post-move reports will trigger a notification to the other party, informing them of the reported movement to them or from them.
• Post-Move Actions: The other party can review, reject, amend, or confirm the movement (refer to the reviewing movement section).
• Pre-Move Actions: The other party can either reject the movement or take no action at this point (refer to the reviewing movement section).

API Information

• API Name for Submitting Movements: XXX

Duplicate Movement Prevention

The service strictly prevents duplicate movement entries to ensure traceability. Each physical movement of animals must have a single movement reference, agreed upon by both parties.

• Duplicate Entry Rejection: Any duplicate movement entry, whether by the same party or the other party, for the same animals between the same locations on the same day will be rejected.
• Single Reporting Requirement: One party (either the sender or receiver) must report the movement, while the other party must review and confirm the information if it is correct.

API Information

• API Name for Submitting Movements: XXX

Confirming Pre-Movement Reports

If a movement was reported before the animals were physically moved (Pre-Move), it must be checked and confirmed on the movement day (or within the legislated reporting window). This ensures that no details have changed.

Process for Confirming Pre-Movements

1. Retrieve the Movement: Access the pre-movement record.
2. Verify Details: The keeper must double-check that all information is accurate and unchanged.
3. Resubmit the Movement: Submit the verified movement again. This submission will then be treated as a post-movement report.

Pre-movement reporting allows keepers to handle reporting in advance, while still accommodating any necessary changes on the actual movement day. Confirming a pre-movement is mandatory if pre-movement reporting is used.

API Information

• API Name for Viewing Movements: XXX
• API Name for Updating Movements: XXX

Reporting Movements for Cattle, Bison, and Bovine Species to and from Ports

Movements involving cattle, bison, and bovine species to and from ports (for export and import) must be reported to the service. These movements are similar to standard movements but require additional information.

Export Movements

When a movement is submitted to a port location, it is identified as an export movement and requires:

• The country and region to which the animals are being exported.
• The date the animals left the country.
• The APHA Import Permit.

Export movements do not trigger a movement review at the port and are automatically confirmed.

Import to Farm Movements

When a movement is submitted from a port to an agricultural holding, it is identified as an import to farm movement and requires:

• The country and region from which the animals were imported.
• The Health Certificate and IPAFFS reference.

Additionally, since these animals need to be registered onto the service (similar to a birth registration), the following details are also required:

• Sire, Dam, Breed, and Date of Birth.
• If the animals are from outside the EU, the original animal number and the new England tag number.

Import to Abattoir Movements

When a movement is submitted from a port to an abattoir, it is identified as an import to abattoir movement and requires the same information as an import to farm movement, plus:

• The Date of Kill.

This ensures that the movement, animal registration, and kill are all reported in a single submission.

API Information

• API Name for Submitting Movements: XXX

Reporting Circular Movements to Show Grounds

When a movement is submitted to a show ground, it is identified as a circular movement. The movement submission can specify whether the animals are planned to return, including the return date if applicable.

Circular Movements

• Planned Return: If the animals are planned to return, the circular movement records both the outbound movement to the show and the return movement to the holding. This movement will be automatically confirmed by the service on the specified return date, eliminating the need for show staff to report these movements.

• No Planned Return: If the animals are not planned to return (e.g., if they are to be sold), the movement will be treated as a normal movement, reporting only the outbound trip to the show. This requires:

• Confirmation by the show.
• Reporting back to the holding by the show.
• Final confirmation by the holding.

API Information

• API Name for Submitting Movements: XXX

Reporting Cross Border Movements

When a movement is submitted to a location outside England, it is identified as a cross-border movement. This can be submitted in the same way as a normal movement, and the service will integrate with either the Welsh or Scottish systems based on the destination.

The process for handling confirmations between the three devolved nations is still being finalized.

API Information

• API Name for Submitting Movements: XXX

Reporting Movements to Common Land

When a movement is submitted to a location designated as common land, it is processed similarly to a normal movement. However, this type of movement does not require confirmation from another party, as no other party is involved.

API Information

• API Name for Submitting Movements: XXX

Reporting Movements Within the Same Business

When a movement is submitted between two locations within the same business, under the same keepership, it is processed like a normal movement. However, it does not require confirmation from another party, as both locations are managed by the same person. These movements can be entered as either sending or receiving.

API Information

• API Name for Submitting Movements: XXX