This process aims to reconcile sales records and/or payments made through card (debit and/or credit) companies, with their respective bills generated in the Protheus Financials Module.
The files sent by the card companies are imported and and processed by the import routine, ensuring data integrity for later reconciliation.
After importing we can reconcile the transactions, in accordance with the automatic rules. We can make manual adjustments, if needed.
The reconciliation is divided in two simplified stages:
Still, there are reports for checking import criticisms and following up on the reconciliations made.
For bills natively generated by the SIGALOJA module, no adjustment is needed. For bills generated by other modules or customized in Financials, the NSU (field E1_NSUTEF) and Authorization Code (field E1_CARTAUT) data are required for the routine to run correctly. Besides this information, depending on system parameter settings (MV_USAMEP), the table SITEF Installments (MEP) must also be updated. |
This feature is available from the version 12.1.27.
\baseline\cartao\Import – Directory in which the files are saved for reading/processing.
\baseline\cartao\Process – Directory in which successfully processed files are automatically saved.
\baseline\cartao\falha – Directory in which files with errors are automatically saved.
To run this process in the SIGALOJA module, register the card companies that must have the "RD - Network" data.
- Reconciled: Correspond to imported sales the counterparts of which (financial bills) were found in accordance with the relationship key: Branch, Site, NSU, Installment, Issue Date, Authorization Code, type "CD" (Automatic Debit Card) or "CC" (Automatic Credit Card) and whether the difference between the value of the sale imported and the value of the financial bill balance is within the tolerance percentage set in routine processing questions.
- Partially Reconciled: Correspond to imported sales the counterparts of which (financial bills) were found in accordance with the relationship key: Branch, Site, NSU, Installment, Issue Date, Authorization Code, type "CD" (Automatic Debit Card) or "CC" (Automatic Credit Card) and whether the difference between the value of the sale imported and the value of the financial bill balance is outside the tolerance percentage set in routine processing questions.
- Bills Without Sales: Correspond to all bills in the database in the period entered in routine processing questions not found in card issuer files.
- Sales Without Bills: Correspond to sales imported from the card issuer and/or card company file the counterparts of which were not found as financial bills, enabling the manual reconciliation of bills available in the database.
- Divergences: Correspond to information available in card issuer or card company files, for manual action of the system user. For example: Total Refund, Partial Refund, Charge Back, Modality Change.
- Totals: Display quantity of records and values processed by date for each of the respective tabs.
- Reconciled: Correspond to imported payments the counterparts of which (financial bills) were found in accordance with the relationship key: Branch, Site, NSU, Installment, Issue Date, type "CD" (Automatic Debit Card) or "CC" (Automatic Credit Card) and whether the difference between the value of the sale imported and the value of the financial bill balance is within the tolerance percentage set in routine processing questions.
- Partially Reconciled: Correspond to imported payments the counterparts of which (financial bills) were found in accordance with the relationship key: Branch, Site, NSU, Installment, Issue Date, Type "CD" (Automatic Debit Card) or "CC" (Automatic Credit Card) and whether the difference between the value of the sale imported and the value of the financial bill balance is outside the tolerance percentage set in routine processing questions.
- Manually Reconciled: Correspond to payments the user has manually reconciled while running this routine.
- Not Reconciled: Correspond to imported payments the counterparts of which (financial bills in Protheus) were not found, enabling manual reconciliation with bills available in the database.
- Divergences: Correspond to information available in card issuer or card company files, for manual action of the system user. For example: Total Refund, Partial Refund, Charge Back, Modality Change.
- Totals: display quantity of records and values processed by date for each of the respective tabs.
- Postings Report
- Bank Statement
- FIF->FIF_NSUTEF
- SE1→E1_NSUTEF
- SL1->L1_NSUTEF
- SL4->L4_NSUTEF
- MDK->MDK_NSUTEF
We currently have the following layouts approved for importing:
|
Possibilita a inclusão de justificativas padronizadas para utilização na tela de conciliação.
Necessário informar um código e uma descrição.
A justificativa será exigida na efetivação dos processos de conciliação das abas: Conciliados Parcialmente, Titulo sem Venda, Venda sem título e Divergentes. |
Possibilita a inclusão de motivos padronizados para utilização na aba de divergências nas rotinas de conciliação.
Necessário informar a operadora, um código e uma descrição para esse motivo.
Os motivos estão documentados nos manuais de cada operadora. |
Possibilita habilitar apenas algumas filiais a utilizarem o processo de conciliação. É usado diretamente no processo de importação dos arquivos.
Necessário informar o código da filial que esta habilitada a importar os arquivos.
Caso nenhuma filial seja cadastrada nessa opção, todas as filiais estarão habilitadas à importarem o arquivo. Quando utilizado o cadastro, apenas as filiais aqui cadastradas é que terão o processo de importação concluído com sucesso. Caso a filial não esteja cadastrada, e um registro for localizado para tal, teremos no log de importação, a informação de que a filial não esta habilitada para importação. |
O processo de importar aquivos contempla somente os layout homologados Software Express, Cielo, Rede e Amex. Esse processo garante a integridade das informações sendo que as críticas serão armazenadas para a análise e providências dos usuários.
- Tela de importação dos arquivos de pagamento/vendas das Operadoras / Administradoras.
- Detalhe dos diretórios de onde os arquivos serão lidos. A importação não leva em consideração a filial em que está sendo feito o processo, visto que os arquivos podem conter mais de um estabelecimento. Sendo assim o controle de filiais é independente do compartilhamento da tabela em questão.
- Após a importação será detalhado um log de críticas por arquivo, sendo possível a identificação de problemas.
Descrição das colunas: As Legendas possíveis para essa tela, o texto do campo Status segue os detalhes da legenda
Nome do arquivo: Detalha o arquivo que foi importado. (O nome do arquivo é usado como forma de controle para evitar duplicidade de processamento) Data Processamento: Data em que foi feita a operação Hora Processamento: Hora em que foi feita a operação Reg. Incluido: Quantidade de registro incluídos na tabela de controle de vendas/pagamentos. (Dependendo do layout/operadora podemos ter conjuntos de linhas para formar uma venda/pagamento) Não Processa: Quantidade de linhas que não foram processas por problemas/criticas.(Detalhe desses processamento pode ser avaliado através do log de importação - FINA917) Linhas lidas: Quantidade de linhas lidas, soma de todas as linha avaliadas pelo programa, considerando inclusive o header, trailer ou qualquer outra linha que não seja processada pela rotina. Tot Lin Arq: Total de linhas do arquivo, refere-se a soma das linhas não processas com as linhas lidas. Cod. Usuário: Código do usuário que fez o processo de importação. Cod. Adm: Código da Administradora/Operadora envolvida na operação. (De acordo com a pasta em que o arquivo foi disponibilizado é definida essa informação)
|
O processo permite a conciliação das vendas importadas com os títulos gravados no sistema. Browse principal demonstra todos os registros de vendas importados e habilitados para essa rotina.
Legenda:
A atualização das legendas ocorre de acordo com a ação dos usuários e o resultado da comparação entre o Protheus e o arquivo das administradoras. ConciliarAo selecionar a opção de conciliar temos a seguinte tela de parametros
Sendo nesse momento é necessário a escolha por conciliar as vendas oriundas do Layout da Software Express ou as vendas oriundas de Demais sendo esse Cielo, Rede e Amex: A diferença entre essas opções esta no fato de seleção de Operadora x Administradora. Para Software Express é possível selecionar entre uma opção de diversas administradoras de cartão, enquanto que Demais só há opções de Cielo, Rede e Amex. Após a seleção será apresentada uma tela com os parâmetros a serem escolhidos: Seleciona Filial: O usuário poderá escolher uma ou mais filiais. O campo será multi-seleção, para conciliação de várias filiais.
Tolerância em %: Percentual do saldo que os títulos podem ter diferenças entre o valor líquido de venda do arquivo importado e o saldo remanescente do título no sistema. Administradora : Ao clicar no ícone "lupa" serão apresentadas as administradoras. O usuário poderá selecionar uma ou mais administradora para conciliar as venda. (Consulta retorna dados específicos de acordo com a seleção Software Express ou Demais) Tipo Processamento: Opção criada para que se escolha como será o tipo de processamento das informações (por aba → mostra os registros somente da aba selecionada) ou (Geral → mostra os registros de todas as abas) Aba para Processamento: Aba a ser utilizada junto com o parâmetro anterior. (1-Conciliados / 2-Conciliados Parcialmente / 3-Títulos sem Venda / 4-Vendas sem título / 5-Divergentes)
O processo de efetivação da conciliação apenas marca a venda como conciliada não demostrando mais esse venda em futuras conciliações. DesconciliarO processo retira as informação de conciliação do registro de venda, permitindo que a venda possa ser conciliada em processos futuros. Processo só pode ser executado caso a conciliação de pagamento não tenha sido executada. |
O relatório de conciliação, apresenta de forma detalhada as vendas com seus correspondentes "status" de conciliação. Parâmetros do relatório:
Operadora ? Seleção da operadora. 1 – Soft. Expres. Bandeira – Software Express ? Selecione a Bandeira para filtrar dados da Software Express. Tecla [F3] disponível para consultar o cadastro de Bandeira. Administradora – Demais ? Selecione a Bandeira para filtrar dados das demais operadora (amex, cielo, rede) Tecla [F3] disponível para consultar o cadastro das administradoras. Seleciona Filiais ? Selecione a opção “Sim” para filtrar as filiais a serem consideradas no relatório ou “Não” para apresentar registros da filial logada. Cliente de ? Selecione o código inicial do intervalo de clientes a serem considerados na geração do relátorio. Tecla [F3] disponível para consultar o cadastro de clientes. Loja de ? Selecione o código inicial do intervalo de lojas de clientes a serem considerados na geração do relatório.
Cliente Até ? Selecione o código final do intervalo de clientes a serem considerados na geração do relatório. Tecla [F3] disponível para consultar o cadastro de clientes. Loja Até ? Selecione o código inicial do intervalo de lojas de clientes a serem considerados na geração do relatório. Num NSU De ? Selecione o código NSU inicial para a geração do relatório. Num NSU Até ? Selecione o código NSU final para a geração do relatório. Data Crédito Inicial ? Selecione a data inicial do crédito para a geração do relatório. Data Crédito Final ? Selecione a data final do crédito para a geração do relatório.
Status Conciliação Pagto ? Selecione os status da conciliação de pagamentos a serem considerados na geração do relatório. Tecla [F3] disponível para consultar as regras. Data Conciliação Pagto. De ? Selecione a data de conciliação de pagamento inicial a ser considerada na geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de pagamento. Data Conciliação Pagto. Até ? Selecione a data de conciliação de pagamento final a ser considerada na geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de pagamento. Usuário Conciliação Vendas ? Selecione o usuário que efetuou a conciliação de vendas para geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de vendas. Deixar o campo branco (vazio) caso queira todos usuários.
Data Conciliação Vendas De ? Selecione a data de conciliação de pagamento inicial a ser considerada na geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de vendas. Data Conciliação Vendas Até ? Selecione a data de conciliação de pagamento final a ser considerada na geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de vendas. Usuário Conciliação Vendas ? Selecione o usuário que efetuou a conciliação de vendas para geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de vendas. Imprime Justificativa ? Selecione a opção "Sim" para imprimir no relatório com as a justificativas da conciliação, caso tenha sido preenchida na efetivação da conciliação. Selecione “Não” para não apresentar a justificativa. Imprime Dados Conciliação ? Selecione a data de conciliação de vendas inicial a ser considerada na geração do relatório. Os registros de vendas (FIF) só estarão com essa data preenchida após a efetivação da conciliação de vendas. Ordem de Impressão ? Selecione a ordem de impressão que deseja ver no relatório. Registro ordenados por: 1 – Conc. / NSU = Ordem de conciliação
|
Log de importação Após finalização da importação dos arquivos através da rotina Wizard (FINA914), o sistema permitirá que se avalie os registros que foram desconsiderados na importação através da rotina de Log´s Importação "TEF (FINA917)". Os status possíveis de cada importação são: Legenda
Na tela de Logs Importação do Tef é possivel: Visualizar Imprimir Outras Ações → Imprimir Browse
Os status Importado parcialmente, Arquivo não importado possibilitam a visualização do detalhe do problema conforme a linha de importação. Quando o status for "Importado Parcialmente", é possível a visualização do detalhe do problema na opção abaixo: Visualizar
Cabeçalho: Status = O ocorrência encontrada no arquivo de acordo com a legenda. Nome arquivo = Nome do arquivo selecionado. Data Process = Data do dia do processamento. Hora Process = Hora do processamento. Reg Incluído = Quantidade de registros de venda/pagamento incluídos (FIF). Não Processa = Quantidade de linhas do arquivo não processadas. Linhas lidas = Quantidade de linhas do arquivo lidas (incluindo as linhas que formaram um registro de venda/pagamento). Tot Lin Arq = Quantidade total de linhas do arquivo. Soma das linhas não processadas com as linhas lidas. Nome Usuário = Nome do usuário logado durante a importação. Nome Adm = Nome da Administradora/Operadora em referencia a pasta em que o arquivo foi disponibilizado. Detalhes: Linha Proc = Linha do arquivo para analise da crítica. Código do Estab = Código do estabelecimento - Utilizado para relacionar o código junto a operadora e a filial do sistema, configurado através do parâmetro (*ver parâmetros). Comprovante = Número do comprovante de venda, entretanto pode ser que o registro criticado não tenha tal informação, só é apresentado com existe na linha avaliada. Motivo = Ocorrência encontrada no arquivo. Em relação aos motivos, temos algumas particularidades. Quando a critica for em relação a não encontrar a Filial ou estabelecimento cadastrado o sistema criticará em apenas uma linha e totalizará as demais linhas com problemas, agrupando esse erro em apenas uma linha, a fim de facilitar a visualização.
ex: Conforme a imagem temos 18 linhas do arquivo com o mesmo código de estabelecimento e esse não esta parametrizado para nenhuma filial com isso todas essas linhas não podem ser processadas. As demais criticas serão apresentadas linha a linha, ou em grupo de linhas dependendo do layout de cada operadora.
Em visualizar também é possível imprimir o Relatório Logs de importação FINR917 com os detalhes que estão na tela sem a necessidade de escolha de parâmetros, basta clicar em "Outras Ações - Imprimir"
Imprimir Permite a impressão do Relatório Logs de importação FINR917, possibilitando a escolha de parâmetros e com todos os detalhes de importação. Imprimir Browse Funcionalidade padrão que permite a impressão do browse atual.
|
 O Browse principal demonstra todos os registros de vendas/pagamentos importados e habilitados para essa rotina. É a partir desse browse que o processo de conciliação inicia. O processo permite a conciliação dos pagamentos, que são os registros provenientes das importações dos arquivos das operadoras: CIELO, REDECARD, AMEX e da Administradora SOFTWARE EXPRESS, com os registros financeiros do contas a receber, que teve como forma de pagamentos: cartão de crédito ou débito. Quando um pagamento for conciliado, o título sofrerá baixa e seu valor entrará no movimento bancário. Legenda:
A atualização das legendas ocorre de acordo com as ações dos usuários, sendo o resultado da comparação entre o Protheus e os arquivos das operadoras: CIELO, REDECARD, AMEX e da Administradora SOFTWARE EXPRESS AlterarHavendo necessidades é possível alterar o campo "status" de um título de venda. Os status que podem ser alterados são:
Baixado : Esse status ocorre quando os pagamentos foram conciliados, pois, nesse processo os títulos são baixados. Divergente: Esse status ocorre quando existirem devoluções total, devoluções parciais, charge back ou troca de modalidades. Não Processado: Esse status ocorre quando os titulo não foram conciliados. É importante ressaltar que os ajustes dos status não estornam a baixa dos títulos. ConciliaçãoAo selecionar a opção de conciliação temos a tela de parâmetros: Software Express ou Demais:
Software Express: conciliação das vendas oriundas do Layout da Software Express. Demais: conciliação das vendas oriundas do Layout Demais sendo: Cielo, Rede e Amex. A diferença entre essas opções esta no fato de seleção da Operadora x Administradora. Para Software Express é possível selecionar diversas administradoras de cartões, enquanto que Demais só há opções de Cielo, Rede e Amex. Após a seleção será apresentada uma tela com os parâmetros a serem preenchidos:
|
Para correto funcionamento do conciliador os parâmetros abaixo devem ser configurados. MV_EMPTEF - Código do estabelecimento configurado para administradora Software Express MV_EMPTCIE - Código do estabelecimento configurado para operadora Cielo MV_EMPTAME - Código do estabelecimento configurado para operadora AMEX MV_EMPTRED - Código do estabelecimento configurado para operadora REDE Todos esses parâmetros devem ser exclusivos representando a Filial que será utilizada no conciliador. Demais parâmetros utilizados pela rotina: MV_USAMEP - Indica se o sistema deve usar a tabela MEP para realizar a conciliação dos arquivos SITEF (T = usa; F = não usa). MV_1DUP - Define inicialização da 1.parcela do titulo gerado Ex. A -> para sequencia alfa 1->para sequencia numérica. MV_LJGERTX - Gera contas a pagar para a administradora financeira com o valor da taxa, e não desconta esta taxa do contas a receber. MV_BXCNAB - Define se as baixas dos títulos no retorno do CNAB devem ser aglutinadas. (S)im ou (N)ão. MV_BLATHD - Quantidade de Threads para o processamento da Conciliação de pagamento. Máximo de 20. MV_BLADOC - Define se a conciliação será feita pelo campo NSU SITEF (FIF_NSUTEF) ou Número do Comprovante (FIF_NUCOMP) |
Pontos de entrada utilizados no processo de importação do arquivo de pagamento (Especifico Software Express) FINFIF - Permite a inclusão de campos no momento da importação do arquivo Software Express - Documento de apoio: http://tdn.totvs.com/x/SX4CE FIN910FIL - Permite alterar o conteudo do campo filial no momento da importação do arquivo Software Express - Documento de apoio: http://tdn.totvs.com/x/s4wDCw Pontos de entrada utilizados no processo de conciliação de pagamento. FINA910F - Define os dados bancários no momento da baixa dos títulos - Documento de apoio: http://tdn.totvs.com/x/X6Vc FA110TOT - Permite a gravação de dados complementares ao registro totalizador da baixa automática de títulos a receber (FINA110) - Documento de apoio: http://tdn.totvs.com/x/2YQDCw |
|
Justification - EFT - FINA911
Enables the addition of standardized justifications to be used on the reconciliation screen.
Enter a code and a description.
The justification will be required when making effective the reconciliation processes of tabs: Partially Reconciled, Bill without Sale, Sales Without Bill and Divergent.
Adjustments Reasons - EFT - FINA912
Enables the addition of standardized reasons for utilization in divergences tab of reconciliation routines.
Enter company, a code and a description for this reason.
Reasons are documented in the manuals of each company.
Branches to Import - FINA913
It enables only some branches to use the reconciliation process. Use it directly in the file import process.
Enter the code of the branch enabled to import the files.
If you do not register any branch in this option, all branches will be enabled to import the file. When you use the register, the import process will only be completed successfully for the branches registered in it.
If you do not register a branch and find a record for it, the import log will inform that the branch is not enabled for import.
Import Wizard - FINA914
The file import process considers only layouts approved for Software Express, Cielo, Rede and Amex. This process ensures data integrity, storing criticisms for users to analyze and take measures.
Premises
Eft.FileDir indicates the directory in which the file will be read.
Proc.FileDir indicates the directory to which the file will be moved after successful processing.
Proc.Inc.Dir indicates the directory to which the file will be moved after processing with error.
Note: to enable fields for input, Card Type must be RD - Rede
- Import screen for payment/sales files from Card Companies.
Correspond to imported sales the counterparts of which (financial bills in Protheus) were found in accordance with the relationship key, Branch, Establishment, NSU, installment, issue date, authorization code, type (Debit/Credit) and tolerance percentage (the tolerance percentage is set in routine parameters).
Tolerance Percentage: Consider that the net sale value must be greater than or equal to the bill balance minus the specified percentage.
Example: Sale
Sale (file) | Bill (Protheus) |
Gross Value BRL 200.00 | Value BRL 195.00 |
Net Value BRL 198.00 | Balance BRL 195.00 |
Tolerance percentage 10% |
Use the following calculation to define whether to fully reconcile it.
Net Value >= Balance - ( Balance * Percentage)
198 >= 195 - (195 * 10%)
198 >= 195 - 19.5
198 >= 175.5
The upper grid shows sales imported through the issuer file, the lower grid shows data from the bill found in the system. The records already appear selected to make the reconciliation effective. You can select item by item or use option "Select All" to change the current selection.
Print the browser in Excel format to analyze the data or to check it later.
Enter the reconciliation type already done to change the status in table, so this record is no longer displayed in future reconciliations.
Correspond to imported sales the counterparts of which (financial bills in Protheus) were found in accordance with the relationship key, Branch, Establishment, NSU, installment, issue date, authorization code, type (Debit/Credit) although "outside" the set tolerance percentage.
Tolerance Percentage: Consider that the net sale value must be smaller than the bill balance minus the specified percentage.
Example: Sale
Sale (file) | Bill (Protheus) |
Gross Value BRL 200.00 | Value BRL 225.00 |
Net Value BRL 198.00 | Balance BRL 225.00 |
Tolerance percentage 10% |
Use the following calculation to define whether to fully reconcile it.
Net Value >= Balance - ( Balance * Percentage)
198 < 225 - (225 * 10%)
198 < 225 - 22.5
198 < 202.5
The upper grid shows sales imported through the issuer file, the lower grid shows data from the bill found in the system. The records already appear selected to make the reconciliation effective. You can select item by item or use option "Select All" to change the current selection.
Print the browser in Excel format to analyze the data or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
Enter type of reconciliation made and save the justification data of said reconciliation, considering it was made outside regular parameters. This update ensures this record is no longer displayed in future reconciliations.
Correspond to all bills found in Protheus not made available in issuer files within the entered sales period (through reconciliation routine parameters) and to corresponding types (Debit/Credit).
The grid shows bills in system that have no sales recorded. You can select item by item or use option "Select All" to change the current selection.
Print the browser in Excel format to analyze the data or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
Create a record on the sales table based on the data of the bill at issue so future reconciliations no longer show it.
Correspond to sales imported from the issuer file the counterparts of which (financial bills in Protheus) were not found in the Protheus database, enabling manual reconciliation with bills available in the database.
The upper grid shows sales imported through the issuer file that were not reconciled. The lower grid shows all bills in the database fit for reconciliation with sales from LOJA.
Print the browser in Excel format to analyze the data or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
IMPORTANT: On this screen (Sales Without Bills) some records from imports may not have their respective bills in financials. In this case you may activate the record with a justification. After this activation, the record will have the status: "Record of Sales Without Bills", which you can view in the browser.
Divergences: contains all sales entered in the card company file with some kind of occurrence, such as: Total Refund, Partial Refund, Charge Back, Modality Change.
Print the browser in Excel format to analyze the data or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
Enter type of reconciliation made and save the justification data of said reconciliation, considering it was made outside regular parameters. This update ensures this record is no longer displayed in future reconciliations.
Totals: display quantity of records with gross and net values in BRL by date for each tab.
The process of reconciliation activation only labels the sale as reconciled, no longer showing this sale in future reconciliations.
The process removes the reconciliation data from the sales record, allowing the sale to be reconciled in future processes. This process can only be executed if the payment reconciliation has not been executed. Reconciliation Report - FINR916 The reconciliation report shows sales in detail with their corresponding reconciliation "statuses". Report Parameters: *Issuer?* Select the issuer. 1 – Soft. Express.2 – Others (Amex, Cielo, Rede). *Card Brand – Software Express?* Select the Card Brand to filter Software Express data. Use the \[F3\] key to query the Card Brand register. *Card Company – Others ?* Select the Brand to filter data from other card companies (Amex, Cielo, Rede). Use the \[F3\] key to query the Card Company register. *Select Branches?* Select option "Yes" to filter branches for the report or "No" to display records from the branch logged. *From Customer?* Select the initial code of the range of customers to be considered for the report generation. Use the \[F3\] key to query the Customers register. *From Store?* Select the initial code of the range of customer stores to be considered for the report generation. *From Customer?* Select the final code of the range of customers to be considered for report generation. Use the \[F3\] key to query the Customers register. *To Store?* Select the initial code of the range of customer stores to be considered for the report generation. *From NSU No.?* Select the initial NSU code to generate the report. *To NSU No.?* Select the final NSU code to generate the report. *Credit Start Date?* Select the start date of credit generate the report. *Credit End Date?* Select the end date of credit to generate the report. *Paymt Reconciliation Status?* Select the payment reconciliation statuses to be considered for report generation. Use the \[F3\] key to query the rules. *From Paymt Reconciliation Date?* Select the payment reconciliation start date to be considered for report generation. Sales records (FIF) will only contain this date after the payment reconciliation becomes effective. *To Paymt Reconciliation Date?* Select the payment reconciliation end date to be considered for report generation. Sales records (FIF) will only contain this date after the payment reconciliation becomes effective. *Sales Reconciliation User?* Select the user who executed the sales reconciliation for report generation. Sales records (FIF) will only contain this date after the sales reconciliation becomes effective. Leave the field blank (empty) if you want all users. *From Sales Reconciliation Date?* Select the payment reconciliation start date to be considered for report generation. Sales records (FIF) will only contain this date after the sales reconciliation becomes effective. *To Sales Reconciliation Date?* Select the payment reconciliation end date to be considered for report generation. Sales records (FIF) will only contain this date after the sales reconciliation becomes effective. *Sales Reconciliation User?* Select the user who executed the sales reconciliation for report generation. Sales records (FIF) will only contain this date after the sales reconciliation becomes effective. *Print Justification? * Select option "Yes" to print reconciliation justifications in report, if filled out at reconciliation activation. Select "No" to not show the justification. *Print Reconciliation Data?* Select the sales reconciliation start date to be considered for report generation. Sales records (FIF) will only contain this date after the sales reconciliation becomes effective. *Printing Order?* Select the printing order to show in the report. Records ordered by: 1 – Recon. / NSU = Reconciliation Order2 – NSU / Recon.= NSU Prder Import Log - FINA917 *Import Log* After you finish importing the files through routine Wizard (FINA914), the system allows you to evaluate records disregarded in the import through routine Import Logs "EFT (FINA917)". The possible statuses of each import are: * Caption* * * |
On the EFT Imports Log screen you can:
View
Print
Other Actions → Print Browser
Statuses Partially Imported, File Not Imported allow viewing problem details in accordance with the import line.
When the status is "Partially Imported", view the problem detail in the option below:
View
Header:
Status = Occurrence found in file in accordance with the caption.
File name = Name of selected file.
Process Date = Date of processing day.
Process Time = Time of processing.
Added Rec = Quantity of sales/payment records added (FIF).
Does Not Process = Quantity of file lines not processed.
Lines Read = Quantity of files lines read (including lines that formed a sales/payment record).
Fi Li Tot = Total quantity of file lines. Sum of lines not processed with lines read.
User Name = Name of user logged during the import.
Co Name = Name of Card Company/Issuer related to the folder in which the file became available.
Details:
Proc Line = Line of file for analysis of criticism.
Estab Code = Code of establishment - Use it to relate the code at the company with the system branch, set in parameter (*see parameters).
Certificate = Number of sales certificate. However, the record criticized may not have this information. It is only displayed if found in the line evaluated.
Reason = Occurrence found in file.
Some particularities are related to the reasons.
When the criticism is related to not finding the Branch or establishment registered, the system criticizes only one line and totals the other lines with problems, grouping this error in only one line to make viewing easier.
Example: as the image shows, we have 18 lines of the file with the same establishment code, the parameters of which are not set for any branch; thus, all these lines cannot be processed.
The other criticisms are displayed line by line or in a group of lines, depending on the layout of each card issuer.
In View you can also Print the Import Logs Report FINR917 with the details onscreen with no need to select parameters. Just click "Other Actions - Print"
Print
Use it to print the Import Logs Report FINR917, setting parameters and including all import details.
Print Browser
Standard feature to print the current browser.
Import Report - FINR917
Printing via Import Logs routine (menu)
The EFT import log report provides details on the logs generated when importing the "EFT (FINA914)" reconciliation files.
You may call the report via menu, through routine Import Logs (FINR917)
Option Print.
Report Parameters.
From File Name? Enter the name of a given import file to print (Start).
To File Name? You can enter the name of a given import file for printing (End).
From Processing Date? Select the date in which you wish to print the report or period (Start).
To Processing Date? Select the date in which you wish to print the report or period (End).
Card Company? Select the card company.
User of Import? Filter by user who executed the file import.
Top header displays the Import Log table data (FVR)
Co Name: Display card company name.
File Name: Display imported file name.
Bottom header displays the Import Log Details table data (FVR)
Proc Line: File line that generated log.
Estab Code: Code of logged line establishment.
Certificate: Number of certificate.
Reason: Display the reason, in detail, why the file line was not included in the import.
Process Date: Display the date of import file processing.
Pro Time: Display the time of import file processing.
Pr.Rec.Qty: Display the quantity of sales/payment records entered in the system that generate EFT reconciliation files (FIF).
Not Pr.Qty: Display the quantity of lines not processed and registered in table FV3
Pr.Ln.Qty: Display the quantity of lines processed. Example: Header, Trailer, sales details, adjustments, etc.
Lines Qty: Shows the sum of lines processed and not processed, adding up to the total of lines in the file. Sum of Not Pr.Qty and Pr.Ln.Qty.
User Name: Display the name of the user responsible for importing the file.
Status: Display the status of file import.
Payment Reconciliation - FINA918
Main browser displays all sales/payment records this routine has imported and enabled. From this browser the reconciliation process begins.
The process reconciles payments, which are records from file imports of the card issuers: CIELO, REDECARD, AMEX and from the Card Company SOFTWARE EXPRESS, with financial records of accounts receivable, which had as payment methods: credit or debit card.
When a payment is reconciled, the bill is posted and its value enters the bank transactions.
Captions are updated in accordance with user actions and the comparative results between Protheus and files from the issuers: CIELO, REDECARD, AMEX and from the Credit Card Company SOFTWARE EXPRESS When files are imported, all records start with "Not Processed", changing status as information is processed.
If needed, you can edit the "status" field of a sales bill. The statuses you can change are:
Posted: This status occurs when payments are reconciled, because this process posts the bills.
Divergent: This status occurs when there are full returns, partial returns, charge back or modality changes.
Not Processed: This status occurs when bills are not reconciled.
It must be emphasized that status adjustments do not reverse bill postings.
When you select option reconcile, we have this parameters screen: Software Express or Others:
Software Express: reconciliation of sales from the Layout of Software Express.
Others: reconciliation of sales from the Layout Others, which are: Cielo, Rede and Amex.
These options differ in the selection of Card Issuer x Card Company. For Software Express, you can select various card companies, whereas Others offers only the Cielo, Rede and Amex options.
After selection, a screen is displayed with parameters you can fill out:
From Branch? : Initial branch to search sales.
To Branch? : Final branch to search sales.
From Credit Date: Start Date of sale reconciliation. (evaluate the issue date of sale).
To Credit Date: End Date of sale reconciliation. (evaluate the issue date of sale).
From NSU No?: NSU Number (Single Sequential Number) that starts the sale reconciliation. (with zeros to the left).
To NSU No.?: NSU Number (Single Sequential Number) that ends the sale reconciliation. (with zeros to the left).
Generation?: Individual - Manually posts bill by bill. By Batch - Automatically posts by batch of bills.
Type?: Select the type to be reconciled. Options: Debit/Credit or Both.
Search Prev Days?: Subtract days from start of selected search. Example: Credit Date 8/20/2018 with this option equal to 2, sales are selected from 8/18/2018.
Tolerance in %?: Percentage of the difference in the bill balances between the net sale value of the imported file and the remaining bill balance in the system
From Financial Company?: Code of initial financial company for the filter.
To Financial Company?: Code of final financial company for the filter.
Posting Date?: Set the date of bill posting. Base Date - day of reconciliation execution and SITEF Credit - Credit date sent in file.
Validate NSU f/ Not Rec.?: Validate in tab "Not Reconciled" whether the relationship between a sale and a bill in financials must have the same NSU.
Select Branches: You can select one or more branches. The field is multiple choice for reconciliation of multiple branches.
From Credit Date: Start Date of sale reconciliation. (evaluate the issue date of sale)
To Credit Date: End Date of sale reconciliation. (evaluate the issue date of sale)
From NSU No?: NSU Number (Single Sequential Number) that starts the sale reconciliation. (with zeros to the left)
To NSU No.?: NSU Number (Single Sequential Number) that ends the sale reconciliation. (with zeros to the left)
Generation?: Individual - Manually posts bill by bill. By Batch - Automatically posts by batch of bills.
Type: Select the type to be reconciled. Options: Debit/Credit or Both.
Search Prev Days?: Subtract days from start of selected search. Example: Credit Date 8/20/2018 with this option equal to 2, sales are selected from 8/18/2018.
Tolerance in %: Percentage of the difference in the bill balances between the net sale value of the imported file and the remaining bill balance in the system
Card Company: Click the "magnifying glass" icon to display card companies. You may select one or more card companies to reconcile sales.
Posting Date? : Set the date of bill posting. Base Date - day of reconciliation execution and SITEF Credit - Credit date sent in file.
Validate NSU f/ Not Rec.? : Validate in tab "Not Reconciled" whether the relationship between a sale and a bill in financials must have the same NSU.
Processing Type?: Option created for you to choose the data processing type (by tab → display records of tab selected only) or (General → display records of all tabs)
Tab for Processing?: Tab to be used along with previous parameter. (1-Reconciled / 2-Partially Reconciled / 3-Bills Without Sales / 4-Sales Without Bills / 5-Divergent)
Correspond to imported sales the counterparts of which (financial bills in Protheus) were found in accordance with the relationship key: Branch, Establishment, NSU, installment, issue date, authorization code, type (Debit/Credit) and tolerance percentage (the tolerance percentage is set in routine parameters).
Tolerance Percentage: Consider that the net sale value must be greater than or equal to the bill balance minus the specified percentage.
Example: Sale
Sale (file) | Bill (Protheus) |
Gross Value BRL 200.00 | Value BRL 195.00 |
Net Value BRL 198.00 | Balance BRL 195.00 |
Tolerance percentage 10% |
Use the following calculation to define whether to fully reconcile it.
Net Value >= Balance - ( Balance * Percentage)
198 >= 195 - (195 * 10%)
198 >= 195 - 19.5
198 >= 175.5
The grid above shows sales, imported through the issuer file, already related with bills found in the system. The records already become fit to be reconciled through button "Activate Reconciliation". Reset item selections by clicking item by item.
To print the upper and lower grids, generated in different tabs, in Excel format for data analysis or to check it later.
When the reconciliation becomes effective, the bills are posted and, consequently, a bank transaction is made based on the option selected in question Generation (Individual or Batch) and the bank balance is updated with the value posted.
Correspond to imported sales the counterparts of which (financial bills in Protheus) were found in accordance with the relationship key, Branch, Establishment, NSU, installment, issue date, type (Debit/Credit) although "outside" the set tolerance percentage.
Tolerance Percentage: Consider that the net sale value must be smaller than the bill balance minus the specified percentage.
Example: Sale
Sale (file) | Bill (Protheus) |
Gross Value BRL 200.00 | Value BRL 225.00 |
Net Value BRL 198.00 | Balance BRL 225.00 |
Tolerance percentage 10% |
Use the following calculation to define whether to fully reconcile it.
Net Value >= Balance - ( Balance * Percentage)
198 < 225 - (225 * 10%)
198 < 225 - 22.5
198 < 202.5
The upper grid shows sales imported through the file from the card issuer and card companies, whereas the lower grid shows data from the bill found in the system. The records already appear selected to make the reconciliation effective. You can select item by item or use option "Select All" to change the current selection.
To print the upper and lower grids, generated in different tabs, in Excel format for data analysis or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
When the reconciliation becomes effective, the bills are posted and, consequently, a bank transaction is made based on the option selected in question Generation (Individual or Batch) and the bank balance is updated with the value posted. Save justification data of said reconciliation, considering it was made outside regular parameters.
Tab "Manually Reconciled" displays bills made effective in tab "Not Reconciled", because in tab not reconciled bills are made effective with justifications and, once confirmed, this record is transferred to tab manually reconciled.
The grid displays sales made effective in tab not reconciled with justifications entered by the operator. This tab displays data in execution time onscreen, that is, it always starts empty, being filled as the manual reconciliations occur.
Print the grid in Excel format to analyze the data or to check it later.
Correspond to sales imported from the issuer files the counterparts of which (financial bills in Protheus) were not found in the Protheus database, enabling manual reconciliation with bills available in the database.
The upper grid shows sales imported through the issuer files that were not reconciled. The lower grid shows all bills in the database fit for reconciliation with sales from SIGALOJA.
If the question at start is Validate NSU f/ Not Rec.?: Is set to YES, the relationship is only allowed if NSU is the same between bill and sale, otherwise the relationship between sale and bill is possible.
To print the upper and lower grids, generated in different tabs, in Excel format for data analysis or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
When the reconciliation becomes effective, the bills are posted and, consequently, a bank transaction is made based on the option selected in question Generation (Individual or Batch) and the bank balance is updated with the value posted. Save justification data of said reconciliation, considering it was made outside regular parameters.
Divergent: contains all sales entered in the card company file with some kind of occurrence, such as: Total Refund, Partial Refund, Charge Back, Modality Change.
Print the grid in Excel format to analyze the data or to check it later.
To correctly control the reconciliation, enter a justification code and a description so you can continue the activation. (you may create the justifications register according to company needs)
Enter type of reconciliation made and save the justification data of said reconciliation, considering it was made outside regular parameters. This update ensures this record is no longer displayed in future reconciliations.
Totals: display quantity of records with gross and net values in BRL by date for each tab.
Print the grid in Excel format to analyze the data or to check it later.
Use option "View Log" to evaluate who executed the payment reconciliation routine. Find the name of the user who executed the process in column "User".
Parameters In Use.
Set the parameters below for the reconciler to operate correctly.
MV_EMPTEF - Establishment code configured for the Software Express card company
MV_EMPTCIE - Establishment code configured for the Cielo card issuer
MV_EMPTAME - Establishment code configured for the AMEX card issuer
MV_EMPTRED - Establishment code configured for the REDE card issuer
All these parameters must be exclusive, representing the Branch to be used in reconciler.
Other parameters used by the routine:
MV_USAMEP - Enter whether the system must use table MEP to reconcile SITEF files (T = uses it; F = does not use it).
MV_1DUP - Define initialization of 1st installment of generated bill. Example: A -> for numeric sequence.
MV_LJGERTX - Generate accounts payable for financial company with rate value, not deducting this rate from accounts receivable.
MV_BXCNAB - Define whether to group bills posted in CNAB return. (S)yes or (N)o.
MV_BLATHD - Quantity of Threads for Payment Reconciliation processing. Maximum of 20.
MV_BLADOC - Define whether to reconcile through field NSU SITEF (FIF_NSUTEF) or Certificate Number (FIF_NUCOMP)
ENTRY POINTS
Entry points used in the payment file import process (Software Express specific)
FINFIF - To add fields when importing the Software Express file - Support Document: {+}http://tdn.totvs.com/x/SX4CE+
FIN910FIL - To edit the contents of file Branch when importing the Software Express file - Support Document: {+}http://tdn.totvs.com/x/s4wDCw+
Entry points used in the payment reconciliation process.
FINA910F - Define bank data when posting bills - Support Document: {+}http://tdn.totvs.com/x/X6Vc+
FA110TOT - To save data complementary to the totalizer record of automatic posting of accounts receivable (FINA110) - Support Document: {+}http://tdn.totvs.com/x/2YQDCw+
Table | Description |
Acronym | FIF |
Name | SITEF Reconciliation File |
Table | Description |
Acronym | FV3 |
Name | EFT Import Log Detail |
Table | Description |
Acronym | FVR |
Name | SITEF Import Logs |
Table | Description |
Acronym | FVX |
Name | Justifications Register |
Table | Description |
Acronym | FVY |
Name | Operator Reasons Register |
Table | Description |
Acronym | FVZ |
Name | Branches to Consider |
Table | Description |
Acronym | MDE |
Name | SITEF Card Company |
Table | Description |
Acronym | MEP |
Name | SITEF Payment in Installments |
For payment reconciliation to work properly, create the fields below.
Field | E1_MSFIL |
Name | Origin branch |
Field | MEP_MSFIL |
Name | Origin branch |
Field | FIF_MSFIL |
Name | Origin branch |
