Overview

The Genesis Manage1to1 integration allows your district to synchronize student fee and payment information between Genesis and Manage1to1.

The integration supports two-way communication:

• Manage1to1 → Genesis: Fees created in Manage1to1 can be added to Genesis.
• Genesis → Manage1to1: Payments recorded in Genesis can be sent back to Manage1to1.

This allows the two systems to remain synchronized without requiring staff to manually enter the same fee and payment information in both systems.

What the Integration Does

Fees

When a fee is created or updated in Manage1to1, the fee information can be sent to Genesis.

Genesis will associate the fee with the appropriate student and create or update the corresponding fee record.

The following information can be included:

• Student
• Fee description
• Fee amount
• Fee category
• Due date
• Account code
• Optional fee designation
• Fee type
• Manage1to1 references

Payments

When a payment is recorded in Genesis for a Manage1to1 fee, Genesis can send the payment information to Manage1to1.

Payment activity includes:

• Payment amount
• Payment date
• Student/fee references
• Payment event ID
• District code
• User who recorded the payment

Waived and declined payments are also communicated using their appropriate event types.

Setting Up the Integration

The Manage1to1 integration is configured through the Genesis Scheduler.

The scheduler task is:

Manage1to1 Sync

The following information is configured for the integration.

Webhook URL

The Webhook URL is supplied by Manage1to1.

Genesis uses this URL when sending payment information from Genesis to Manage1to1.

Shared Secret

The Shared Secret is supplied by Manage1to1 and is used to securely authenticate payment requests sent from Genesis.

The Webhook URL and Shared Secret must both be configured before Genesis can send payments to Manage1to1.

Schools

You can select which schools should participate in the payment export.

Only payments associated with the selected schools will be included in the scheduled payment export.

Payment Export Options

The Manage1to1 Sync scheduler includes options for controlling payment exports.

Test Mode

Test Mode allows you to verify what Genesis would send to Manage1to1 without actually sending the payment information.

When Test Mode is enabled, Genesis records the payment information in the integration log instead of sending it to Manage1to1.

This can be useful when initially configuring or testing the integration.

Export Payments

The Export Payments option enables the scheduled payment export.

When enabled, Genesis identifies eligible payments and sends them to Manage1to1.

Export Date

An Export Date must be specified when exporting payments.

Genesis uses this date as the starting point for determining which payments should be exported.

The selected date cannot be a future date.

Fee Categories

Manage1to1 fees use Genesis fee categories.

Before sending a fee to Genesis, Manage1to1 must provide a valid Genesis fee category code.

Only fee categories that are active and not retired can be used.

Genesis provides an API endpoint that allows Manage1to1 to retrieve the district's available fee categories.

If a fee is submitted using an invalid, inactive, or retired category, the fee will not be imported.

Optional Fees

Manage1to1 can identify a fee as optional.

When an optional fee is received by Genesis, Genesis stores the fee as an optional fee.

Optional fees are also identified as optional in the parent notification when a new optional fee is added.

New Fees in Genesis

When Genesis receives a new fee from Manage1to1:

1. Genesis identifies the student.
2. Genesis validates the fee information.
3. Genesis validates the fee category.
4. Genesis creates the fee.
5. Genesis associates the fee with the student.
6. If applicable, parents are notified that a new fee has been added.

If the fee already exists, Genesis updates the existing fee instead of creating a duplicate.

Updating Existing Fees

Manage1to1 uses a fee line reference to identify individual fee records.

When Genesis receives a fee with a line reference that already exists, the existing Genesis fee is updated.

The following information can be updated:

• Amount
• Description
• Fee category
• Due date
• Optional status
• Account code
• Fee type

This prevents duplicate fees from being created when an existing Manage1to1 fee is updated.

Deleting Fees

Manage1to1 can request that a fee be removed from Genesis.

Genesis identifies the fee using the Manage1to1 references associated with the fee.

Fees with no payments

If the fee does not have any payments, Genesis can remove the student fee.

If no other students are associated with the underlying fee, Genesis also removes the fee itself.

Fees with payments

A fee that already has payments cannot be deleted through the Manage1to1 integration.

This protects payment history and prevents a fee with financial activity from being removed.

If Manage1to1 attempts to delete a fee that has payments, Genesis returns an error indicating that the fee cannot be deleted.

Payment Synchronization

When an eligible payment is recorded in Genesis, the payment can be sent to Manage1to1.

Genesis verifies that the payment contains the information required to associate it with the Manage1to1 fee.

A payment will not be sent if:

• It was already sent to Manage1to1.
• The associated fee does not contain a Manage1to1 reference.
• The associated student fee does not contain the required Manage1to1 reference.
• The fee is configured to be excluded from the payment vendor.
• The fee does not have a description.
• The student associated with the payment cannot be found.
• The generated payment information is invalid.

Payment Statuses

Genesis communicates different types of payment activity to Manage1to1.

This allows Manage1to1 to distinguish between a normal payment and other types of payment activity.

Preventing Duplicate Payments

Once Genesis successfully sends a payment to Manage1to1, the payment is marked as Sent to Vendor.

This prevents the same payment from being sent again during a subsequent export.

If Manage1to1 returns an error or does not provide a successful response, Genesis does not mark the payment as successfully exported.

Security

Payment requests sent from Genesis to Manage1to1 are authenticated using the configured Shared Secret.

Genesis creates a security signature for each request and includes it with the payment request.

The request also contains a timestamp to help ensure that requests are current.

The following headers are included:

X-Genesis-Timestamp X-Genesis-Signature

The Shared Secret should be treated as confidential and should only be provided to authorized personnel.

Troubleshooting

Payments are not being sent

Check the following:

1. Confirm that the Manage1to1 Sync scheduler task is enabled.
2. Verify that the Webhook URL is configured.
3. Verify that the Shared Secret is configured.
4. Confirm that the correct schools are selected.
5. Verify that the Export Date has been entered.
6. Check the Manage1to1 Sync logs for errors.

A fee was not imported

Verify that:

• The student exists in Genesis.
• The fee contains a valid external_ref.
• The fee contains a valid student ID.
• The fee contains a creation date.
• At least one charge was included.
• The charge contains a line_ref.
• The fee category exists in Genesis and is active.
• The charge contains a valid amount.
• The charge contains a valid due date.

The API response will identify skipped records and provide an error describing why the record was not imported.

A fee cannot be deleted

If Genesis reports that the fee has payments and cannot be deleted, the fee must remain in Genesis because payment history is associated with it.

Manage1to1 reports an authentication error

Verify that:

• The Webhook URL is correct.
• The Shared Secret matches the value supplied by Manage1to1.
• The Manage1to1 endpoint is available.

Genesis logs unsuccessful responses from Manage1to1 under the Manage1to1 Sync log category.

Integration Logging

Manage1to1 integration activity is recorded under:

Category: MANAGE1TO1_SYNC

Log Name: Manage1to1 Sync

The logs can be used to investigate:

• Fees that were skipped
• Invalid fee information
• Missing students
• Invalid fee categories
• Payment export failures
• Responses from Manage1to1
• Successfully exported payments
• Test Mode payment exports

When contacting Genesis support about an integration issue, providing the relevant Manage1to1 Sync log information can help identify the problem.

Recommended Setup Process

For a new district, the recommended setup process is:

1. Obtain the Webhook URL from Manage1to1.
2. Obtain the Shared Secret from Manage1to1.
3. Configure the Manage1to1 Sync scheduler task in Genesis.
4. Select the schools that should participate.
5. Enter the appropriate Export Date.
6. Enable Test Mode.
7. Review the generated test payment information in the logs.
8. Once the configuration has been verified, disable Test Mode.
9. Enable payment exporting.
10. Monitor the Manage1to1 Sync logs for successful exports and errors.

Summary

The Manage1to1 integration provides automated synchronization between Genesis and Manage1to1.

Manage1to1 → Genesis

• Creates fees
• Updates existing fees
• Identifies optional fees
• Deletes eligible fees
• Associates fees with students

Genesis → Manage1to1

• Sends payments
• Sends waiver activity
• Sends reversal activity
• Prevents duplicate payment exports
• Authenticates requests securely

Once configured, the integration minimizes the need for staff to manually maintain the same fee and payment information in both systems.