<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="432847" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="29/10/2026" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="695,117,971,1000" />
         <classifier id="Layer" value="Layer 1"/>
          <classifier id="numcol" value="1"/>
         <classifier id="ArticleStyle" value=""/>
       <classifier id="Epaper-Build" value="7.1.5.2"/>
  <classifier id="ProcessingDateTime" value="Wed Oct 28 2026 20:31:35 GMT+0600"/>
      </identified-content>

      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20261029T000000+5.30" edition.name="Business" edition.area="BUS" position.section="DST29102604BUS-BIZBACK" position.sequence="4" ex-ref="DST29102604BUS-BIZBACK.indd" />
  </head>
  <body boxBorderWeightColor="#000000" boxBorderWeight="0.25">
<body.head>
      <hedline>
    	<hl1 id="Headline1" ul="0" ol="0" ulColor=""  ulWeight=""  olColor=""  olWeight="" textFrameColor="" orgstyle="HEAD new 25 MEDIUM" class="1" MainHead="true" style="Headline1">
		<lang class="3" colour="#000000" orgstyle="HEAD new 25 MEDIUM" style="Headline1"  font="Antonia H1" fontStyle="Medium" size="29">Make payer names mandatory in digital payments </lang>
	</hl1>

       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
		<media-reference id="tn" source-credit="" data-location="1" source="ImageOfGroup9436_4_BUS_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
	</media>
</block>

     <p style=".Bodylaser" ul="0" ol="0"  orgstyle="BY NAME_2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BY NAME_2025" font="Impact" fontStyle="Regular" size="9">▌</lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BY NAME_2025" font="Antonia H1" fontStyle="Bold" size="9">	MIZANUR RAHMAN
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="INDENTLESS BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="INDENTLESS BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Electronic payments have freed businesses and institutions from the trouble of collecting, carrying and depositing cheques. Yet a basic question can remain unanswered after a transfer reaches an account: who paid this money? The payer’s name should be a mandatory field for every electronic transfer and should appear in the recipient’s payment record.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The problem occurs in both government and private corporate payments. Some bank statements identify the payer, making reconciliation straightforward. Others include only a generic description or the name of a bank. An organisation receiving many payments must match each credit to a customer and an invoice. Without the payer’s identity, a completed transfer can remain unresolved in its accounts.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Consider a statement I recently reviewed. On a single day in June, it showed a series of government electronic funds transfer (EFT) credits in different amounts, each carrying essentially the same description: ‘EFT Inflow//MOTIJHEEL/TREASURY S/Government’. The amounts and transaction numbers were visible, but the names of the offices making the payments were not. A private company’s transfer creates the same difficulty when its name is missing from the credit record.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The practical consequence is easy to see. An accounts team can confirm that money has arrived but cannot confidently assign it to the correct payer. Staff then have to request payment advice, compare amounts with outstanding bills and contact the bank or the paying offices. Sometimes the match is clear; sometimes several bills have similar amounts. Meanwhile, a payer who has already transferred the money may still appear to owe it. That can strain a relationship, despite neither party being at fault.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The problem becomes even more serious at the end of the financial year, when a large number of unidentified receipts may remain unreconciled. This can lead to an understatement of reported revenue, inaccurate outstanding receivables and significant weaknesses in the year-end audit process. What begins as a missing payer name can ultimately affect the reliability of an organisation’s financial statements.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">I see the benefit of EFT in my own work. A newspaper may receive payment for a small advertisement from a government institution in a distant district. Previously, collecting a Tk 10,000 cheque could mean sending someone to the office, couriering the cheque to Dhaka and asking another colleague to deposit it. Electronic transfers remove much of that effort. But the gain is partly undone if we must spend hours identifying the receipt afterwards.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The Bangladesh Bank should require the actual paying person, company or government office to be identified in a mandatory payer-name field. The name must be captured when the transfer is initiated, passed through the payment system and displayed by the receiving bank in the statement or credit advice. A field that can be left blank, replaced with “Government” or reduced to the bank’s name would defeat the purpose.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">A bill or invoice reference would further help recipients match payments, and banks should make transaction numbers easy to trace. But those additions do not replace the essential requirement: every recipient should be able to see who paid. The same rule should apply whether the money comes from a government office or a private company.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Digitisation succeeds when the entire process becomes easier, including the accounting that follows payment. A visible payer name enhances transparency and accountability for both sender and recipient. Making payer identity mandatory is a simple, practical step towards that goal.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium Italic" size="9">The writer is the chief financial officer and head of operations of The Daily Star</lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">
</lang>
</p>

    </body.content>
  </body>
</nitf>