Skip to content
Login | Support
KTL Solutions
  • Home
  • Platforms
    • Microsoft Office 365
    • Microsoft Dynamics 365 – ERP
    • Microsoft Dynamics 365 – CRM
    • Microsoft Azure
      • CMMC Preparedness
    • Microsoft Power Platform
    • Microsoft Government Cloud
      • GCC
      • GCC-High
      • Azure Government Cloud
  • KTL Products & Services
    • KTL 360 Managed Services
      • KTL 360 Commercial Services
      • KTL 360 Government Services
    • KTL Custom Development
    • KTL Products
  • Company
    • About Us
    • Careers
    • Events
  • Blog
  • Contact Us
  • Home
  • Platforms
    • Microsoft Office 365
    • Microsoft Dynamics 365 – ERP
    • Microsoft Dynamics 365 – CRM
    • Microsoft Azure
      • CMMC Preparedness
    • Microsoft Power Platform
    • Microsoft Government Cloud
      • GCC
      • GCC-High
      • Azure Government Cloud
  • KTL Products & Services
    • KTL 360 Managed Services
      • KTL 360 Commercial Services
      • KTL 360 Government Services
    • KTL Custom Development
    • KTL Products
  • Company
    • About Us
    • Careers
    • Events
  • Blog
  • Contact Us
Teams Collaboration

Jeff Chamberlain

4 Easy Steps to Safe Pay

  • June 11, 2015
  • , 2:10 pm
  • , ERP, Technology

What is Safe Pay?

Safe Pay or Positive Pay is a program provided by the bank for the purposes of theft / fraud protection.  The Company setting up Safe Pay will provide a file to the bank.  This file should include the Company’s Bank Account Number –   Check Number – Issue Date – Amount.  When a check is presented to the Bank for payment it is compared to this list.  If the fields do not match exactly the check will not be paid and the company / user will receive an exception notification.  At that point the company / user would instruct the bank to either pay the check or return the check.

The Safe Pay file may include Accounts Payable checks / Payroll Checks and EFT Transactions.  Direct Deposit Payroll transactions are not included in the Safe Pay file.  These transactions are submitted via ACH and not subject to the bank’s check clearing procedures.

Initial Steps before Configuring SafePay

Sample file from Bank – Contact your Bank and have a sample file layout from them prior to starting the configuration of Safe Pay.  This will help insure the configuration / setup is correct.

Have a Plan to Test the File with Bank – Having a Plan to Test the first file generated from your system will ensure that it is acceptable by the Bank before you begin generating the file in your production environment.  Once your file is created and uploaded to the Bank – the file can’t be recreated.  Prior to sending – the file may be edited in Notepad – but this is not the optimal solution.  It is better to have the file automatically generated correctly by the system.

Once you have the 2 steps listed above in place – it is time to Setup Safe Pay. 

Setup Safe Pay / Configure Safe Pay

Go to Financial >> Routines >> Safe Pay >> Configurator

This will open the Safe Pay Configurator Window.

Step 1--Name the Format

Setup a Bank Format and Description – These are required Fields.  Example Bank Format could be the Bank Name / Description could be Bank Name and File Type – as seen in the example below.

Click Save before proceeding to Step 2.

Step 2 – Create Output Record Lines – This is where you will create only the lines that are necessary and will appear on the output file for transmission to the bank.  The Detail Record Line is always a required line by the Bank.

OutPut Type – Select from the Drop Down List.  Refer to the bank documentation for requirements. 

  • Fixed Field
  • Comma Delimited
  • Tab Delimited

Record Type – Select from the Drop Down List.  All banks require the Detail – Account Line.  Header / Footer Information may be optional.  Refer to the bank documentation for requirements.

  • Header – transmission
  • Header – Account
  • Detail – Account
  • Footer – Account
  • Footer – Transmission

Line Name – Used as a Description Only  – Must be Unique – not included in the file that is transmitted to the bank.

# of Fields – Indicates the number of fields to be defined.  Using the Delimited file from above – we will configure 5 fields.

# of Characters – Only if using the Fixed Length Output Type

Click Save

Enter additional line names as required by your bank.

Step 3 – Edit Record Fields – This is where you will add Field Names and Define the Output fields

Highlight a field setup in Step 2 – this will populate the Edit Record Fields box.

Double Click on a line in Step 3 – this will Open the Output Fields Window where the criteria for this field will be defined.  This window will auto-populate with the Field Number – this cannot be changed.

Field Name – This is a required field and must be unique.

Standard Fields – Select a standard field from the drop down list that matches the field from the bank documentation for that line.  Using our example from above – Field 1 is Account Number – select Account Number from the drop down list.

Field Type – From the bank documentation – Select the Field Type for that field.  In our example the bank documentation specifies Numeric.

Field Format – Used to Further Define some Field Types.

Number of characters – Used Only if using Fixed File Format

Click Save when Done

Enter the OutPut Field Information for each Field listed in Step 3.

Step 4 – Transaction Codes

Click on Codes Entry in the Menu Bar of the Safe Pay Configurator Window

This will open the Transaction Type Entry Window.

Codes need to be setup for each transaction type that will be included in the output file.  Currently the output file only includes Checks & Voids.  These codes should be listed in the bank documentation you received.

Output Format – auto-populates from the previous screen.

Transaction Type – Identifies the type of transaction.

  • Check
  • Void
  • EFT

Matching Code – Enter the code from your bank documentation

Click Save – this will return you to the Safe Pay Configurator Window

Click Save.

You have now setup Safe Pay.  In the next installment we will go over generating the Safe Pay File and Transmitting that file to the Bank.

Have questions or want to learn more about this process? Contact Tricia at 301.360.0001 or email at sales@ktlsolutions.com


TRICIA CHASE | Senior Business Software Consultant

As a Senior Business Consultant, Tricia has performed various roles for customers including conducting design sessions, integrating data, training GP and 3rd Party modules, troubleshooting data issues, and acting as interim controller. Tricia has over 20 years of experience as an accountant and over 15 years of experience with Microsoft Dynamics GP usually working with the Accounting / Finance Teams or the HR / Payroll Teams.  Prior to KTL, Tricia worked for various partners and as an Independent Consultant.  She has worked with various industries including:  Construction, Trucking, Health Care, and State Government.  Tricia holds a B.S. in Accounting from St. Mary of the Plains College in Dodge City, Kansas.

Share this post

Tags
365 2013 2015 2016 accounting BI blog Business Business Intelligence Cloud CMMC CRM Data Development Dynamics Dynamics 365 Dynamics CRM Dynamics GP ERP Excel Government Contractor GP How To ISV KTL KTL Blog KTL Solutions Management Microsoft Microsoft Dynamics Microsoft Dynamics CRM Microsoft Dynamics GP Office 365 Power BI Project Project Management Reports Sales Security Solutions Technology tools User User Conference Webinar

Recent Posts

  • The System Security Plan: Outline to Your Organization’s Journey Towards NIST SP 800-171 Compliance
  • Keeping Up with the Industry: KTL eLearning
  • DFARS Interim Final – CMMC writing is on the wall even if the ink isn’t dry yet
  • KTL Solutions Partners with EBizCharge to Deliver Credit Card Processing within Microsoft Dynamics
  • Webinar Recap: Top Ten New Features in the Microsoft Dynamics 365 and Business Central 2022 Wave 2 Releases

Categories

  • Azure Government
  • BI
  • Blog
  • Business Central
  • CMMC
  • CRM
  • Customization
  • Dynamics 365
  • ERP
  • Events
  • Exclusive Content
  • GCC-High
  • How Tos
  • KTL Products
  • Managed Services
  • Microsoft 365
  • Microsoft Dynamics GP
  • Modern Workplace
  • Project Management
  • Technology
  • Uncategorized

Related Posts

The System Security Plan: Outline to Your Organization’s Journey Towards NIST SP 800-171 Compliance

When people ask me, “what is the single most important document to have to start working towards complying with DFARS clause 252.204-7012 and NIST SP 800-171?”, I always point them to their System Security Plan (SSP). Wait, what?

Read More »
January 23, 2023

Keeping Up with the Industry: KTL eLearning

With KTL eLearning, your business can provide ongoing compliance and standard governance training, which will increase your employees’ knowledge base and minimize internal help desk tickets.

Read More »
January 9, 2023

DFARS Interim Final – CMMC writing is on the wall even if the ink isn’t dry yet

There has been much discussion around the Cybersecurity Maturity Model Certification (CMMC) and if it is going away. This topic can prove to be confusing, and we want to help. Let’s break down the current view of the CMMC program and what is happening.

Read More »
January 5, 2023

KTL Solutions Partners with EBizCharge to Deliver Credit Card Processing within Microsoft Dynamics

The partnership between KTL Solutions and EBizCharge will allow merchants to process payments directly within Microsoft Dynamics, providing new productivity gains, lower processing fees, and enhanced data security.

Read More »
November 23, 2022
Delivering tailored solutions so you get the most out of your technology
Facebook-f Twitter Linkedin-in Youtube

Quick Links

  • Platforms
  • KTL 360 Managed Services
  • KTL Custom Development
  • KTL Products

About

  • Company
  • Careers
  • Blog
  • Support Log In

Newsletter

Sign up for our mailing list to get the latest updates and offers.

Subscribe to Our Newsletter
  • 866.960.0001

© All rights reserved

Terms of Use | Privacy Policy

Designed by Papersword B2B