There are 2 things you should be doing to make the code easier to understand and maintain. #1 is the logical use of blank lines to separate different concepts and proceses.

Illogical spacing: 

  open('conf', "$PATHconf") || die "can't open $PATHconf: $!\n";
  my @conf = <conf>;
  close('conf');
  my $i=0;
  foreach(@conf){
  my $line = $conf[$i];
  
    my $t= "".$i;
    my $dbhA = DBI->connect("DBI:mysql:$VARDB_database:$VARDB_server:$
+VARDB_port", "$VARDB_user", "$VARDB_pass")
    or die "Couldn't connect to database: " . DBI->errstr;

    my $rowCount = 0;
    
    my $filename = "Output012023.xlsx";
    my $workbook = Excel::Writer::XLSX->new( $filename );
    open(FH, "<", "Debt.csv" ) or die;

[download]
Logical spacing: 
  open('conf', "$PATHconf") || die "can't open $PATHconf: $!\n";
  my @conf = <conf>;
  close('conf');

  my $i=0;

  foreach(@conf){

    my $line = $conf[$i];
    my $t    = "".$i;

    my $dbhA = DBI->connect("DBI:mysql:$VARDB_database:$VARDB_server:$
+VARDB_port", "$VARDB_user", "$VARDB_pass")
    or die "Couldn't connect to database: " . DBI->errstr;

    my $rowCount = 0;    
    my $filename = "Output012023.xlsx";
    my $workbook = Excel::Writer::XLSX->new( $filename );

    open(FH, "<", "Debt.csv" ) or die;

[download]
#2 is to add a comment every time you figure something out: 
  foreach(@conf){

    my $line = $conf[$i];
    # the reason for doing this weird thing
    my $t.   = "".$i;

[download]
The comments will significantly reduce the cognitive load needed to comprehend the code by outsourcing all the reasons for this and that to brief human readable comments.

In reply to Re^9: bug or curly bracket hell? by Anonymous Monk
in thread bug or curly bracket hell? by MoodyDreams999

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.